FIX: Errors Running Wizards Against Objects not Owned by DBO (239133)

The information in this article applies to:

Microsoft SQL Server 7.0

This article was previously published under Q239133

BUG #: 56147 (SQLBUG_70)
BUG #: 55515 (SQLBUG_70)

SYMPTOMS

When you run SQL Server Enterprise Manager wizards against objects owned by anyone other than yourself or the database owner (DBO), you may receive errors and the wizard may not complete successfully.

CAUSE

When you do not use the fully qualified object name, SQL Server looks for the following:

<current server>.<db specified>.<user logged on>.<object specified>

If it does not find this, it then looks for this:

<current server>.<db specified>.dbo.<object specified>

The wizards do not allow you to specify an owner. So, if you are not logged on as the object owner and the object is not owned by the DBO, the wizards will not find the object.

WORKAROUND

Use sp_changeobjectowner to change the owner of the table to the DBO, and then run the wizard again.

STATUS

Microsoft has confirmed this to be a problem in SQL Server 7.0. This problem has been corrected in U.S. Service Pack 2 for Microsoft SQL Server 7.0. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

254561 INF: How to Obtain Service Pack 2 for Microsoft SQL Server 7.0 and Microsoft Data Engine (MSDE) 1.0

For more information, contact your primary support provider.

MORE INFORMATION

One example of this problem is that when you run the Index Tuning Wizard on tables that neither you nor the DBO own, you will receive the following error:

The server returned an error attempting to either create a temporary table or index statistics.

Another example of this is that when you run the Create View Wizard and use tables that neither you nor the DBO own, you will receive the following error:

Error 21776: [SQL-DMO]The name '<object name>' was not found in the Tables collection. If the name is a qualified name, use [] to separate various parts of the name, and try again.

Modification Type:	Major	Last Reviewed:	3/14/2006
Keywords:	kbBug kbfix KB239133