BUG: Not All Database Options Transfer from Model to New DB

Last reviewed: February 20, 1998
Article ID: Q181555
The information in this article applies to:
  • Microsoft SQL Server, versions 6.0 and 6.5
BUG #: 17820 (SQL 6.5)

SYMPTOMS

When creating a new database, only the following database options will be transferred from the model database to the new database:

   Select Into/Bulk Copy
   Truncate Log on Checkpoint

The following databases options are not transferred to the new database:

   Columns Null by Default
   No Checkpoint on Recovery
   Single User
   DBO Use Only
   Read Only

WORKAROUND

To work around this problem and set the desired database options, do either of the following:

  • Double-click the database in SQL Enterprise Manager, select the Edit Database Options dialog tab, and select the appropriate option check boxes.

    -or-

  • Run the sp_dboption stored procedure.

    For example, to set the "Columns Null by Default" option in a database, execute the following statements from a query window (where <dbname> is the name of the database where the change will occur):

          use master
          go
          sp_dboption <db_name>, "ANSI null default", true
          go
    

STATUS

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


Additional query words: defaults settings checkbox checkboxes
Keywords : kbbug6.00 kbbug6.50 SSrvAdmin
Version : WINNT:6.0,6.5
Platform : winnt
Issue type : kbbug
Solution Type : kbworkaround


THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: February 20, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.