FIX: Error 21761 When Binding Non-DBO Default

This article was previously published under Q202429
This article has been archived. It is offered "as is" and will no longer be updated.
BUG #: 53106 (SQLBUG_70)
SYMPTOMS
When a user of a database other than the database owner (DBO) creates a default using SQL Server Enterprise Manager and the DBO then tries to bind the default to a column of a table in that database using Enterprise Manager, the following error occurs:
Error 21761: [SQL-DMO]Default Default name not found.
CAUSE
The SQL Server Enterprise Manager calls the sp_bindefault stored procedure with the parameters default name and column name. While passing the default name, Enterprise Manager does not qualify the default name with name of the object owner.
WORKAROUND
To work around this problem, bind the default using the sp_bindefault stored procedure in SQL Server Query Analyzer. Make sure the default name is fully qualified, as in the following example:
database name.user name.default name
For example, to bind the default "my_default", created by the user "guest", to the qty column of the sales table in the pubs database, you would execute the following:
sp_bindefault 'pubs.guest.my_default', 'sales.qty'				
STATUS
Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 1 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
232570INF: How to Obtain Service Pack 1 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0
For more information, contact your primary support provider.
ent man entman err message msg
Properties

Article ID: 202429 - Last Review: 10/11/2013 21:56:07 - Revision: 2.1

  • Microsoft SQL Server 7.0 Standard Edition
  • kbnosurvey kbarchive kbbug kbfix KB202429
Feedback