Microsoft KB Archive/114525

{|
 * width="100%"|

The information in this article applies to: - Microsoft SQL Server Programmer's Toolkit, version 4.2 BUG# 9437 (4.2b)

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 SQL Server version 4.2b for OS/2. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
 * }

-

Last reviewed: April 29, 1997

© 1998 Microsoft Corporation. All rights reserved. Terms of Use.