Home > Archive > MS SQL Server > May 2005 > Maximum databases on SQL Server 2000









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author Maximum databases on SQL Server 2000
Dave

2005-05-21, 3:23 am

We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )

This server is being used for heavy analysis by 10 heveyduty workstations.

We have more then 1000 databases on this server.

Should we limit the databases on this server ? we are having issues with
performance and SQL service stopping frequently..

Please advise
Joe Yong

2005-05-21, 3:23 am

Probably. I'd be surprised you can keep all 1000 open and working at the
same time. Memory, disks, bus, etc... are all probably pretty upset with
their deplorable work conditions. :-)

Figure out which of your 1000 databases are most heavily used and move them
out first. Perfmon and Profiler are probably gonna be your new buddies if
they aren't already.

Btw, perf issues aside, 1000 databases in one instance is probably not much
fun to manage. Just expanding the object browser takes a while. What about
maintenance operations? Look up multi instance in BOL and give it some
serious thought. Life will probably be at least a little better that way.


joe.

"Dave" <Dave@discussions.microsoft.com> wrote in message
news:37CBC0C7-C1FA-4FE5-9851- B101A5E8E88D@microso
ft.com...
> We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
>
> This server is being used for heavy analysis by 10 heveyduty
> workstations.
>
> We have more then 1000 databases on this server.
>
> Should we limit the databases on this server ? we are having issues with
> performance and SQL service stopping frequently..
>
> Please advise



Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2008 droptable.com