|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Maximum databases on SQL Server 2000
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 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. Show quoteHide quote "Dave" <D***@discussions.microsoft.com> wrote in message news:37CBC0C7-C1FA-4FE5-9851-B101A5E8E88D@microsoft.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
Other interesting topics
Shrinking the Transaction Log
Access 97 to SQL Fiscal or Calendar Year Function error CASE Statement reliable way to identify all dependencies? DB Consistency Errors occurring frequently on random tables database marked as "Suspect" altering a primary key property Compare tables layout in dev and prod nested "starting up database" in the logs |
|||||||||||||||||||||||