Enterprise Manager runs slow on some computers

I have a network of WinXP SP1 machines who all connect to
SQL Server 2000 SP3 on a Win2k server. When running
enterprise manager, most of the computers take at least 4
minutes to expand the database tree. Working on databases
(retrieving properties etc) is also painfully slow. On
two computers, however, Enterprise Manager shows no
slowdown and work as I would expect. Can anyone assist me
in diagnosing the problem?
I would guess that one of the snap ins on the slower machines might be
causing a problem, I had something similar happen to me only for me the
enterprise manager wouldn't open at all.
On one of the slower machines try opening the Microsoft Management Console
program (C:\windows\system32\mmc.exe) and click on file and add/remove snap
ins. CLick the Add button and then select the Microsoft SQL Enterprise
manager. Click Ok and then try to open the database tree to see if its any
quicker. If so you can then click save as and use this console file instead
of the enterprise manager. If not then I'm afraid i can;t help you.
Nick
"G. Sutherland" <g.sutherland@.REMOVEkildrummy.co.uk> wrote in message
news:5dbc01c474b6$da345870$a501280a@.phx.gbl...
> I have a network of WinXP SP1 machines who all connect to
> SQL Server 2000 SP3 on a Win2k server. When running
> enterprise manager, most of the computers take at least 4
> minutes to expand the database tree. Working on databases
> (retrieving properties etc) is also painfully slow. On
> two computers, however, Enterprise Manager shows no
> slowdown and work as I would expect. Can anyone assist me
> in diagnosing the problem?
|||Check to ensure that the AutoClose properties of the databases are not set
in EM on the slow machines.
Andrew J. Kelly SQL MVP
"G. Sutherland" <g.sutherland@.REMOVEkildrummy.co.uk> wrote in message
news:5dbc01c474b6$da345870$a501280a@.phx.gbl...
> I have a network of WinXP SP1 machines who all connect to
> SQL Server 2000 SP3 on a Win2k server. When running
> enterprise manager, most of the computers take at least 4
> minutes to expand the database tree. Working on databases
> (retrieving properties etc) is also painfully slow. On
> two computers, however, Enterprise Manager shows no
> slowdown and work as I would expect. Can anyone assist me
> in diagnosing the problem?
|||Check for a file called SQL.LOG on the slow machines. If it's there and is
growing, you've got ODBC Tracing turned on.
Otherwise, run a network trace and compare the protocols being used from
the slow vs. fast.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
|||Also, in EM, you can click on File|Options... and choose to delete the
history of changes to the console files. This can speed up performance as
well.
Jacco Schalkwijk
SQL Server MVP
"G. Sutherland" <g.sutherland@.REMOVEkildrummy.co.uk> wrote in message
news:5dbc01c474b6$da345870$a501280a@.phx.gbl...
>I have a network of WinXP SP1 machines who all connect to
> SQL Server 2000 SP3 on a Win2k server. When running
> enterprise manager, most of the computers take at least 4
> minutes to expand the database tree. Working on databases
> (retrieving properties etc) is also painfully slow. On
> two computers, however, Enterprise Manager shows no
> slowdown and work as I would expect. Can anyone assist me
> in diagnosing the problem?
|||Yes you fixed my prob-, SQL TRACING WAS TURNED ON.
I have a very fast computer and it still made E-P-M very slow alymost
unuseable... Found c:\sql.log file 2.5 GB's in size ha ha...
Turned Tracing off works very fast now. cool!
Hummm, Now to find out how it got turned on in the first place ? Who
did it did you ? why you little #&*&#?! get over here!
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!