Enterprise Manager connection to Local server very sloooow.

Hi,
I'm having a problem connecting to a local copy of SQL server 2000 using
enterprise manager (on Win2k). Doing anything, connecting, refreshing
list of tables etc. takes a very long time (>10secs) slower even than
remote connections.
Also, the enterprise manager itself becomes doggedly slow - eg. tringing
to move a window across the screen is difficult becuase it is so
stuttery. I have checked task manager, and it's not using much CPU time
though.
One other clue is that when you use something like the DTS wizard, the
local server is not explicitly displayed as one of the available servers.
This has only started happening recently. Any ideas on what is going on?
Thanks!
Check to see if you have the Auto-Close option turned on any of your databases.
and check to see if OBDC tracing is turned on.
|||Thanks. Auto-Close was turned on, ODBC tracing was not.
I've turned auto-close off now, and this seems to have helped quite a
lot. Still a bit slow though, so makes me think there is something else
going on.
Any idea why the local server would not be displayed in the 'select
server' dropdown?

> Check to see if you have the Auto-Close option turned on any of your databases.
> and check to see if OBDC tracing is turned on.
>
|||Thanks. Auto-Close was turned on, ODBC tracing was not.
I've turned auto-close off now, and this seems to have helped quite a
lot. Still a bit slow though, so makes me think there is something else
going on.
Any idea why the local server would not be displayed in the 'select
server' dropdown?

> Check to see if you have the Auto-Close option turned on any of your databases.
> and check to see if OBDC tracing is turned on.
>
|||Sosh123 wrote:[vbcol=seagreen]
> Thanks. Auto-Close was turned on, ODBC tracing was not.
> I've turned auto-close off now, and this seems to have helped quite a
> lot. Still a bit slow though, so makes me think there is something
> else going on.
> Any idea why the local server would not be displayed in the 'select
> server' dropdown?
Did you check all your databases for Auto-Close?
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Also check to make sure that none of the network components between you and
the server have their network connections set to Auto-negotiate, especially
through a switch. The protocol is not standardize and oftentimes will set
everything to 10 Mb, Half-duplex.
Also check your SQLEM Options to NOT reconnect to last connection on
relauch.
Sincerely,
Anthony Thomas

"David Gugick" <david.gugick-nospam@.quest.com> wrote in message
news:%23BhAFC7ZFHA.3620@.TK2MSFTNGP09.phx.gbl...
Sosh123 wrote:[vbcol=seagreen]
> Thanks. Auto-Close was turned on, ODBC tracing was not.
> I've turned auto-close off now, and this seems to have helped quite a
> lot. Still a bit slow though, so makes me think there is something
> else going on.
> Any idea why the local server would not be displayed in the 'select
> server' dropdown?
Did you check all your databases for Auto-Close?
David Gugick
Quest Software
www.imceda.com
www.quest.com