Hi

Having 100's of databases does slow EM down as it need to list them all.
That is about it.

Regards
--------------------------------
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland

IM: mike@epprecht.net

MVP Program: http://www.microsoft.com/mvp

Blog: http://www.msmvps.com/epprecht/

<mike@rumblegroup.com> wrote in message
news:1112124274.309091.156730@f14g2000cwb.googlegr oups.com...
> Hi,
>
> I am trying to determine what the overhead is per database in SQL
> Server 2000 Standard. I have the option to put several customers in one
> database, or give each customer their own database. I would like to put
> each customer in their own database to simplify maintenance and
> strengthen security.
>
> I have found the following document which shows the memory used by
> various objects in SQL Server:
>
>
http://msdn.microsoft.com/library/de...ar_ts_8dbn.asp
>
> Based on this info I get the following *additional* memory requirements
> per database:
>
> Open Database (1 file, 1 filegroup): 6k
> Open Objects (250 objects, 30 indexes): 692k
> Total: 698k
>
> Is this an accurate calculation of the overhead? Is there something
> else that would affect the overhead that I am overlooking? Are there
> any other downsides to having many databases versus a few databases?
>
> Thanks,
> Mike
>