BUG: SEM/SQL-DMO Abnormally Terminates w/ Large Objects

• Microsoft SQL Server version 6.0

SYMPTOMS

From several points in the SQL Enterprise Manager (SEM) application, the SQL-DMO function DBObject::Script() is invoked. If the object to be scripted nears the 64K text limit, then SEM will simply disappear.

CAUSE

Actions such as Manage Triggers, Manager Stored Procedures,and Generate Scripts can all manifest behavior of the sequence:

1. Script of the object is near 64K of text



2. SEM simply disappears without a GPF or warning message



3. SQL-DMO function DBObject::Script causes application to abnormally abort

WORKAROUND

Install the OBJECT60.SQL script and use version 4.21a's Object Manager to generate the scripts for triggers and stored procedures.

Be sure not to check the Table Triggers or the Stored Procedures option when generating the rest of the object definitions from SEM.

STATUS

Microsoft has confirmed this to be a problem in Microsoft SQL Server version 6.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.

Additional query words: sql6 sem

Keywords : kbtool SSrvAdmin SSrvDMO SSrvEntMan kbbug6.00
Version : winnt:6.0
Platform : winnt
Issue type :