Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Can a large number of schemas present a problem in some ways (performance, maintenance)? By large I mean a few thousands, and schemas will mostly contain views, fetching data from shared tables.

share|improve this question
up vote 3 down vote accepted

Since SQL Server can handle up to 2,147,483,647 objects in a database, I suspect that having thousands of schemas will only incrementally cause slowness. (Just like anything else, the more different things you have the more processing you need.)

I imagine that your biggest problem will be remaining organized with thousands of schemas to manage. Depending on what you are trying to accomplish, there may be other approaches. For example, row and cell level security.

You might have seen this before, but here is a 2005 paper on implementing row and cell security.

I have done row/cell security without implementing everything in this paper. So, if that looks better to you, then be judicious in choosing the level of complexity.

share|improve this answer
That article is a huge help, thanks! – Evgeni Mar 22 '14 at 18:09

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.