FIX: Object Manager Fails if SA's Default DB is Not Master
  
PSS ID Number: Q112248
Article last modified on 11-07-1994
 
4.20
 
WINDOWS
 

----------------------------------------------------------------------
The information in this article applies to:
 
  - Microsoft SQL Server version 4.2
----------------------------------------------------------------------
 
BUG# 9437 (4.2)
 
SYMPTOMS
========
 
Running OBJECT2.SQL will fail with the following error message,
 
   The following objects were not created.
   Sql Object Manager will not run against this server
 
if the SA's default database is not master.
 
CAUSE
=====
 
There is no 'use master' in the beginning of the OBJECT2.SQL. If the
SA's default database is not 'master', the new objects will be
created in the user db.
 
At the end of the script, it checks to see if the new objects exist
in master.dbo.sysobjects and removes the stored procedure
'sp_MSOM_version' so that the SQL Object Manager tool cannot connect
to SQL Server afterwards.
 
WORKAROUND
==========
 
Change the SA's default database to master; for example, run
'sp_defaultdb sa, master', then run the script OBJECT2.SQL. After it
is done, you can change the default database back to the user
database.
 
Or add 'use master
     go'
at the beginning of OBJECT2.SQL.
 
STATUS
======
 
Microsoft has confirmed this to be a problem in Microsoft SQL Server
version 4.2. This problem was corrected in Microsoft SQL Server version
4.21. For more information, contact your primary support provider.
 
Additional reference words: 4.20 4.20b tool Windows NT
KBCategory: kbother
KBSubcategory: SSrvGen SSrvWinNT SSrvObj_Man
 
=============================================================================
 
Copyright Microsoft Corporation 1994.
