We are using a propriety SQL Server 2012 database, from a company that has given it's tables, views, objects, etc a schema name – lets call it COMP, for "the company's" schema.
We, as the client, are allowed to have full access to the company's database structure via SSMS, and have full control of all aspects of it. However, in order for us to customise the database to our needs, we've created a separate schema called INT, for "our internal" schema. Our new tables, views, etc are all under this schema and everyone is happy.
However, our "INT" schema has an hour job we run that seems (have not confirmed yet), to lock the entire database including the company's schema and structure. This in effect locks the application, at the users' end for at least 3 to 5 minutes. Some users have already noticed this and have started to raise complaints.
Some of our views in our INT schema, do refer to COMP schema tables and objects. Could that be why it's locking everything? Is there a way to separate our schema from the COMP schema of objects so it doesn't lock or hog the server to all users? Is there best practice on how to do the above please?