Hello,
I am being asked to support a third part y app that will create a new database per session with upwards of 500 databases being created per month, now I know that this is not good but my bosses are asking for the technical reasons why this is not good, can someone help please? There are the obvious #of databases to maintain ie backup etc but what else can I add?
Thanks
Julian
I can think of a couple. First is memory consumption. Each open database will have in memory structures that consume virtual address space. See this article for one of the issues:http://support.microsoft.com/kb/316749/en-us
There is also some disk space implications. Each new database will need it's own system tables, allocation pages, Index roots, etc. Say this adds up to even 2mb per database that's 1000 MB/month just for metadata. If everything were in a single database you could safely assume only a few MB total over the life of the database for metadata and allocation pages.
Next is sheer capacity of the server. SQL Server currently supports 32767 databases, at over 500 databases/month that will get you by for about 65 months. Do you really want to go with a solution that will leave you high and dry after a few years.
not to mention the overhead of trying to replicate schema or index changes to thousands of databases.
HTH
-Jerome
No comments:
Post a Comment