enterprise manager slow to load on shared server with 200 databases

My db is on a shared server with two hundred tiny databases. Query
analyzer connects very fast, buty Enterprise Manager stupidly reads the
schema for each of the 200 db's while it is loading the GUI. Sadly, it
freezes up for about ten minutes while loading all that stuff.
I love the way EM makes admin a breeze. Is there a way (registry tweak
or something) to make it so it will just show the databases my account
has access to (like query analyzer does)
Thanks, Tom
Nope...you can change the system stored procedures that
Enterprise Manager calls. You can learn to use Query
Analyzer more or write your own utility that works like
query analyzer. A lot of it is written using SQL-DMO. You
can also use SQL-NS for some of the user interface
components invoked with Enterprise Manager. Both SQL-DMO and
SQL-NS are documented in books online.
-Sue
On 1 Mar 2005 16:44:39 -0800, thomasamillergoogle@.yahoo.com
wrote:

>My db is on a shared server with two hundred tiny databases. Query
>analyzer connects very fast, buty Enterprise Manager stupidly reads the
>schema for each of the 200 db's while it is loading the GUI. Sadly, it
>freezes up for about ten minutes while loading all that stuff.
>I love the way EM makes admin a breeze. Is there a way (registry tweak
>or something) to make it so it will just show the databases my account
>has access to (like query analyzer does)
>Thanks, Tom
|||In addition to what Sue recommends make sure you don't have Auto Close
turned on with any of the db's.
Andrew J. Kelly SQL MVP
<thomasamillergoogle@.yahoo.com> wrote in message
news:1109724279.921121.305760@.l41g2000cwc.googlegr oups.com...
> My db is on a shared server with two hundred tiny databases. Query
> analyzer connects very fast, buty Enterprise Manager stupidly reads the
> schema for each of the 200 db's while it is loading the GUI. Sadly, it
> freezes up for about ten minutes while loading all that stuff.
> I love the way EM makes admin a breeze. Is there a way (registry tweak
> or something) to make it so it will just show the databases my account
> has access to (like query analyzer does)
> Thanks, Tom
>
|||Sorry, I don't think i have enough time on my hands to rewrite
Enterprise Manager :P
What stored procedures could be changed to speed up the way it loads
the databases when the databases node is expanded?
Sql-NS looks fascinating, i never knew about that. Looks cool!
Thanks, Tom
Sue Hoegemeier wrote:[vbcol=seagreen]
> Nope...you can change the system stored procedures that
> Enterprise Manager calls. You can learn to use Query
> Analyzer more or write your own utility that works like
> query analyzer. A lot of it is written using SQL-DMO. You
> can also use SQL-NS for some of the user interface
> components invoked with Enterprise Manager. Both SQL-DMO and
> SQL-NS are documented in books online.
> -Sue
> On 1 Mar 2005 16:44:39 -0800, thomasamillergoogle@.yahoo.com
> wrote:
the[vbcol=seagreen]
it[vbcol=seagreen]
tweak[vbcol=seagreen]
account[vbcol=seagreen]
|||Hi Tom,
No...don't think anyone has enough time to rewrite it but
thought I'd mention it as it is an option. Maybe not a
realistic one but an option nonetheless.
Anyway...it calls system stored procedures. Changing those
means you will no longer be running a supported system and
could end up with more problems than you solve. It's just
best not to go there. If you want to see what it's calling,
just run profiler and get a trace of what's executed.
Make sure you check for autoclose as Andrew mentioned...I
forgot about that. And make sure you are on the latest
service pack as there have been some fixes in some of the
service packs related to enterprise manager and it's
performance. And also make sure you don't have ODBC tracing
turned on. You can check the ODBC Administrator applet and
check the Tracing tab to see if it's on.
And then...one other option I just thought of. I don't know
about all of the third party tools but maybe one of those
has the functionality you need without some of the overhead
you are experiencing with Enterprise Manager. You may want
to look at those. You can find a list of them at:
http://www.aspfaq.com/show.asp?id=2442
Hope that helps -
-Sue
On 2 Mar 2005 08:37:15 -0800, thomasamillergoogle@.yahoo.com
wrote:
[vbcol=seagreen]
>Sorry, I don't think i have enough time on my hands to rewrite
>Enterprise Manager :P
>What stored procedures could be changed to speed up the way it loads
>the databases when the databases node is expanded?
>Sql-NS looks fascinating, i never knew about that. Looks cool!
>Thanks, Tom
>
>Sue Hoegemeier wrote:
>the
>it
>tweak
>account
|||Thanks Sue, that more than helps. Much appreciated I have learned more
from you reply then in my last hundred posts to usenet .
I passed on the sql-ns and sql-dmo items to a friend who is devleoping
a sql server front end, he *really* likes it !
Tom
|||FYI, DMO and sql-ns is being replaced by SMO in SQL2005. So he may want to
check that out as well.
Andrew J. Kelly SQL MVP
<tom.a.miller@.gmail.com> wrote in message
news:1109881960.302088.148920@.f14g2000cwb.googlegr oups.com...
> Thanks Sue, that more than helps. Much appreciated I have learned more
> from you reply then in my last hundred posts to usenet .
> I passed on the sql-ns and sql-dmo items to a friend who is devleoping
> a sql server front end, he *really* likes it !
> Tom
>
|||Good to hear and thanks!
-Sue
On 3 Mar 2005 12:32:40 -0800, tom.a.miller@.gmail.com wrote:

>Thanks Sue, that more than helps. Much appreciated I have learned more
>from you reply then in my last hundred posts to usenet .
>I passed on the sql-ns and sql-dmo items to a friend who is devleoping
>a sql server front end, he *really* likes it !
>Tom
|||If anybody else is having this problem, I solved it by installing sql
server 2000 service pack 3, which updated the client tool (enterprise
manager). It still freezes up the EM ui but only for about a minute or
so.