Article ID: 918040 - View products that this article applies to.
Bug #: 423365 (SQLBUDT)
Consider the following scenario. You detach or back up a database that is in an instance of SQL Server 2005. The instance of SQL Server 2005 is running on Server A. Later, you attach or restore that database to an instance of SQL Server 2005 that is running on Server B. In this scenario, you may experience the following symptoms:
This problem occurs because the login that you use to create the database on Server A is not in the instance of SQL Server 2005 on Server B. This login could be either the Microsoft Windows login or the SQL Server login.
To work around this problem, use one of the following methods.
Note Before you use the following methods, make sure that you enable the Trustworthy database property.
If you access the CLR object from a different database, and that database has a mismatching DBO SID, the same problem can occur.
For more information, visit the following blog:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the CREATE LOGIN statement, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/ms189751.aspxFor more information about the sp_changedbowner stored procedure, visit the following MSDN Web site:
http://msdn2.microsoft.com/en-us/library/ms178630.aspxFor more information about the CREATE ASSEMBLY statement, visit the following MSDN Web site:
Article ID: 918040 - Last Review: April 8, 2010 - Revision: 3.0