RE: Open default DB in Enterprise Manager upon connecting to server (S

Question 1:

This is indeed a problem with SQL 2000.
I heard it has something to do with SQL loading all databas + tables in
memory first.
This will not happen in SQL 2005 ;)

Question 2:
I don't thin you can, but i am not sure.
Maybe you can better connect with SQL Query Analyzer.
--
I drank alot of beer and ended up in the police department database.
Drank more beer and learned SQL in the dark hours.
DELETE FROM offenders WHERE Title=''MrAA'' AND Year=2006;
I love SQL :)




"Vsevolod Ukrainsky" wrote:

FYI: my sincere apologizes if this group is not the right place for my
questions.

Hello,

1. My hosting provider hosts ~500 databases on the server where my DB
resides. To open my database I use SQL Server 2000 Enterprise Manager.

While server connection timeout is short enough (about 1-2 seconds), when I
click "Databases" folder in server hierarchy, trying to enlist all
databases, it takes and extremely long period of time to set up a list.
Moreover - 60% of attempts usually fail. - Enterprise Manager hangs deadly
and its process could be terminated only by Task Manager.

My first question is: why does EM take such a timeout to display a list of
databases and why in most cases it halts?

2. To open my database and to start working with it I each time have to
perform the above steps. However I find it rather silly - to enlist all
databases first and ONLY THEN select mine. Logical approach to the process
of database connection suggests NOT to enlist all databases (I really need
only one!), but configure server (client?) that way that upon connecting to
server it automatically defaults to my DB.

My second question is:
Has SQL Server 2000 Enterprise Manager such a feature? Can I configure it
not to enlist all databases upon connecting to server, but switch directly
to mine by default?

Thank you in advance.
Vsevolod.



.

Relevant Pages

  • Re: Side-by-side upgrade - moving master, msdb and model
    ... MVP - Windows Server - Clustering ... "In some cases, you may want to copy the system databases, including ... from the source SQL Server 2000 instance to the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: BizTalk Server 2004 ConfigFramework.exe error
    ... one BizTalk is installed on? ... machines (both for SQL and DTC) is not blocked by firewalls and new MSDTC ... Multi-computer configuration using Windows Server 2003 or Windows XP ... >>all associated databases. ...
    (microsoft.public.biztalk.general)
  • RE: Clustering a standalone SQL server + storage array
    ... working as expected with out error your ready to install sql server. ... log files to the data and log shared drives you setup as part of the cluster. ... Our apps team look after a trading system that uses an HP DL360 server ... running SQL 2000 SP3a with a few small databases on it. ...
    (microsoft.public.sqlserver.clustering)
  • Re: Side-by-side upgrade - moving master, msdb and model
    ... MVP - Windows Server - Clustering ... "In some cases, you may want to copy the system databases, including the ... from the source SQL Server 2000 instance to the SQL ...
    (microsoft.public.sqlserver.clustering)
  • Re: SQL 2005 servers with multiple instances
    ... Microsoft SQL Server MVP ... given the same number of user databases. ... we've decided to use SQL 2005. ... SQL 2005 clustering? ...
    (microsoft.public.sqlserver.setup)