In Microsoft SQL Server 2005 Service Pack 2 (SP2), the following tasks in a maintenance plan may lose database context in certain circumstances:

• Check Database Integrity
• Execute T-SQL Statement

For example, if a Check Database Integrity task is configured to check integrity on multiple databases, the task repeatedly checks the default database.

For the Execute T-SQL Statement task, this problem occurs if the following conditions are true:

• The Execute T-SQL Statement task contains multiple batches.
• The batches are separated by the GO statement.
• No batches use the USE statement to specify the database.
• The statements in each batch do not contain the database name.

In this scenario, those statements in the second batch and in succeeding batches will be executed against the default database.

Note You can confirm that this problem has occurred by using SQL Server Profiler. When you trace the maintenance plan execution, see the Database column in SQL Server Profiler.

This problem occurs in SQL Server 2005 builds 3042 through 3053 and in SQL Server 2005 builds 3150 through 3158. If you are running a build of SQL Server 2005 SP2 between 3150 and 3158, download and install the following file from the Microsoft Download Center.
The following file is available for download from the Microsoft Download Center:

Collapse this imageExpand this image

Download the SQL2005-KB934459-ENU package now. (http://www.microsoft.com/downloads/details.aspx?FamilyId=A7C903FE-35A7-4BB2-8E73-932770099711&displaylang=en)

If you are running any build of SQL Server 2005 SP2 between 3042 and 3053, click the following article number to view the article in the Microsoft Knowledge Base:

APPLIES TO

For More Info: http://support.microsoft.com/kb/934459