Hi: It takes me about 10 to 15 minutes to actually connect to sql database here is a screenshot http://www.pixpond.com/xx/jodoshared.jpg
is this normal?
If not how can i fix it?
It takes me quite a while to load, too. But not 10 to 15 minutes. It takes maybe 20-25 seconds or something mildly annoying like that. That time-test is over a DS3 line, but I looked at my bandwidth usage during that time and it was very small. I would think that it would take about the same amount of time for a dial-up user, but I don’t really know. I have DSL at home and it is about the same as here at work with the DS3.
thanks for the reply . Its a serious annoyance I know. However once I connect its fairly fast my other problem is more serious see
http://support.jodohost.com/showthread.php?t=2534
I have dial-up too and it takes 10-15 minutes here to.. this is because of the large amounts of data Enterprise Manager downloads..
weird MS hasn’t made it so that only databases where the logged in user has access is downloaded..
The load time is mostly dependant on latency (ping time) to the database server, not bandwidth.
For some reason the Enterprise Manager basically requests all the database information 1 database at a time instead of in bulk.
On a LAN this isn’t so much of a problem, but on long distance connections it can have disastrous results like this.
From the times I have observed it’s actually even worse and the program seems to make multiple roundtrips to get all information on a database.
Let’s assume you have a 300ms ping time because you’re in Australia, and that every database causes 3 requests for information from the Manager client. Now there’s also 300’ish databases on the server, so the minimal theoretical time it would take to load the entire list (assuming infinite bandwidth and program response speeds) would be: 3003300 = 270,000ms = 4,5 minutes.
I don’t have any actual numbers, but as you can see this can quickly amount to long response times, while the same data exchange could theoretically be done within a second on a broadband line if only it was done in bulk.
Basically the Enterprise Manager is not designed to work over an internet connection. Loading only the databases one actually has access to would be very helpful without requiring a large rewrite of any of the software, but it’s not gonna happen 
SQL Server 2005 is in beta at the moment, perhaps that will improve things eventually. From the feature list I understand the management tools have been changed rather extensively.
just wanted to add my response times have improved dramatically. Now it is only a few seconds before I connect. 
Its all the dang DB’s that load. Once it has them reconnecting is quick. Query Analizer only connects to the DB you have permission to though.
Say where did you get Enterprise Manager and how much was it?
the client tools are the most useful…
Re EM taking a long time to display the list of databases in the database folder is a known issue with SQL Server 2000 and can be resolved installing the latest SQL Server 2000 Service Pack. It must be resolved on client’s machine. Please follow this link for instruction on how to resolve the problem: http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q282/4/16.ASP&NoWebContent=1
hth ~megan
Thanks for this link, Megan. The update increased my Enterprise Manager access time from something over 5 minutes to 30 to 40 seconds!
You’re quite welcome 
~megan
would anyone please care to check if access to their database is available through enterprise manager. My client seems to show no items available in the database console tree.
Thanks.
nm seems to working now