Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Enterprise Manager Expand Databases Slow

Status
Not open for further replies.

rac2

Programmer
Apr 26, 2001
1,871
US
After upgrading to SQL Server 2000, Enterprise Manager now needs about 10 minutes to display the list of 70 databases.
My Client Network Utility has TCP/IP enabled. Any suggestions?
 
Is this being done from the same machine as the SQL Server or from a remote system?

There's lots of reasons that could be causing this, so it's going to be hard for us to help you solve it.

Some issues:
1. what kind of system is it on?
2. is this an upgrade from SQL Server 7? or from SQL Server 2000 Standard?
3. what other applications are running on the server?

You might not have a system 'powerful' enough to run the Enterprise Edition. That could be causing the slow down. Check out this webpage:
Important thing to note: MEMORY. Enterprise Edition: 64 megabytes (MB) of RAM; 128 MB recommended
While it can use the same minimum memory as Standard (64 mb), Microsoft recommends 128 MB.


-SQLBill

Posting advice: FAQ481-4875
 
The problem is on remote computers, EM works OK on the local machine. Did I say Enterprise Edition? Im sorry I meant to say Enterprise Manager. The upgrade was from SQL Server 7 to SQL Server 2000 Standard Edition. The server is on a machine with NT5.0, 511MB OS Memory, two processors.

 
Do your databases have the autoclose option turned on?

When you launch Enterprise Manager and get the list of databases you have to connect to each database on the server to find out if you have access to that database (you can see this in profiler if you setup a trace). Setting up a trace might not be a bad idea. You will be able to see if the problem is the server taking forever to process your requests, or network traffic, etc.

I would recommend putting some more memory in that machine. Windows 2000 (NT 5) needs at least 128 to it self, leaving about 384 for your SQL Server. Unless your SQL Server isn't doing much, while that is technically enough for SQL Server to use, in reallity an upgrade would be well worth the money.

If you log into the SQL Server's console and open up Enterprise Manager do you have the same problem? While you are logged in check the memory usage in task manager. What's the memory used? Memory available? How are the CPUs doing?

Denny

--Anything is possible. All it takes is a little research. (Me)

[noevil]
(My very old site)
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top