BUG: Sp_certify_removable Db_name, Auto Fails If Case Sensitive

Last reviewed: April 17, 1997
Article ID: Q157733

The information in this article applies to:

Microsoft SQL Server, version 6.5

BUG #: 16218 (NT: 6.50)

SYMPTOMS

Sp_certify_removable "db_name", AUTO fails with error 15258 instead of giving ownership of the database and all database objects to the systems administrator (SA) and dropping any user-created database users and any permissions they may have.

CAUSE

When you run sp_certify_removable with the AUTO option, it calls sp_check_removable with the 'Auto' parameter. Inside sp_check_removable, the input parameter is tested with the value 'auto' instead of 'Auto'. This problem does not occur with a case insensitive sort order.

WORKAROUND

To work around this problem, install SQLServer with an insensitive sort order.

STATUS

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

Keywords : kbbug6.50 SsrvTran_SQL
Version : 6.5
Platform : WINNT
Issue type : kbbug
Resolution 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: April 17, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.