BUG: Database Restore May Result in DBO Mismatch if DBO Has Been Changed More Than Once (296437)
The information in this article applies to:
- Microsoft SQL Server 2000 (all editions)
This article was previously published under Q296437
BUG #: 353636 (SHILOH_BUGS)
SYMPTOMS
Restoring a database backup that was created while a previous login owned the database may result in a database owner (DBO) mismatch. After the database is restored, the sp_helpdb and sp_helpuser procedures may return different DBOs for that database.
CAUSE
The database backup contains DBO information from before the ownership change, while the master database contains the current ownership information. The restore operation does not reset the database owner.
WORKAROUND
You can work around this problem in the following ways:
- Make sure that a full database backup is performed each time that database ownership is changed, and restore only this (or later) backups of the database.
- Log in to the SQL Server as a member of the sysadmins group and execute the sp_changedbowner procedure to change the owner of the target database to the correct login.
STATUS
Microsoft has confirmed this to be a problem in SQL Server 2000.
Modification Type: | Major | Last Reviewed: | 11/19/2003 |
---|
Keywords: | kbbug kbpending KB296437 |
---|
|