Server Fault is a question and answer site for system and network administrators. 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

I'm in the middle of designing a software system storing data in about 4000 tables in Microsoft SQL Server 2008. Does anyone have any pointers to ease management of such a large number of tables?


P.S.: It's already normalized.

share|improve this question
What problems are you having? Most database scripts are already set up to handle multiple tables. – Sam Aug 11 '09 at 21:10
I'm curious to know what type of system uses 4000 tables too! – Sam Aug 11 '09 at 21:11
Dear God... Are these all performing unique functions? – squillman Aug 11 '09 at 21:24
Sam: sp_foreachtable will be very handy I'm sure. I'm not really concerned about SQL Server's capabilities as much as the process of keeping it organized for people to understand. It's an ERP system. – AJ. Aug 11 '09 at 21:32
up vote 0 down vote accepted

Use declarative Policy-Based Management instead of managing individual tables.

share|improve this answer
Ooh... I like this. – AJ. Aug 12 '09 at 18:08

About the only suggestion I can offer is learn to love the filter icon in SSMS to make it easier to find the objects you are looking for.

share|improve this answer

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.