Speed problem in Enterprise Manager

I hope someone here can can give me some advice. I'm setting up a website that uses SQL Server 2000 for data storage needs. I'm able to connect to my database just fine, whether it be by Query Analyzer, Enterprise Manager, or my application. However, Enterprise Manager is painfully slow when I first bring it up. I followed the instructions in the FAQ section for setting up Enterprise Manager to use with my database. However, when I first go to that database group and expand the list of databases, it actually downloads ALL the databases and I can see them. I can't go in and look at or edit/view tables or anything like that, but they are listed. I have to go all the way down the list, find my database, and that's the one I can work with.

Is there anyway to speed database list download up? It takes a couple of minutes to access my database thru Enterprise Manager. Seems like the best way to speed things up would be to limit the list of databases to the one I actually own, but I have no idea how to do this. Funny thing is, Query Analyzer doesn't do this. It goes straight to my database each time. Any ideas?

Thanks!



cms

 

Ahh!! Thanks Bruce!! I'll do it ASAP!!!


cms

 

Well, I installed SP3a. Good news it seems to have helped but it still takes too long. I can't believe MS had it so it pulls back every stinking database. Seems like you should be able to define which database you want look at in EM. Oh well, thanks!



cms

 

I ran into this problem on another server...

One way around the problem is to use the "Data Access Project" mode of MS Access 2000 and on.

You can Create a new "data access project" (DAP) with Access on your PC and connect it to your SQL server database. Then when you open the DAP, it will connect directly to your SQL Server database. You are limited to what you can do, but for browsing data it's great.

I'm no expert but I got it working just by using the Access Help. Start off by using File/New menu and select "Project (Existing Database)"

SaveAs Type should be "Microsoft Access Project". Just pick a filename to save your connection (select this next time to reopen the connection). Then it will popup a box to enter your DataLink Properties. Enter your db sever info from your SQL Server control panel. eg: server name: mssql03.discountasp.net


Phil.

 

Someone pointed out that ?this issue is fixed in sp3a? that is incorrect, it has not been fixed.

Also the comment that ?EM was not designed to be used over a WAN only on a local machine?.

That is not true; it was designed to be used over a WAN, just poorly designed.

It is an absolutely fundamental requirement for any product competing in this space to have a networked solution; let alone the solution from one of the top DB products in the world.

This may be fixed by Microsoft in the next product and then again it may not.

Mike