FIX: "Server: Msg 7359" error when you run a distributed query in SQL Server 2008 or in SQL Server 2008 R2 if a schema version is updated more than five times

Article translations Article translations
Article ID: 2588970 - View products that this article applies to.
Expand all | Collapse all

On This Page

Microsoft distributes Microsoft SQL Server 2008 Service Pack 2 (SP2) or Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 or SQL Server 2008 R2 update release.

SYMPTOMS

Consider the following scenario:
  • You create a linked server on a computer that is running Microsoft SQL Server 2008 or Microsoft SQL Server 2008 R2. The linked server points to an OLE DB data source on a remote server.
  • You run a distributed query that uses some data objects on the linked server.
  • You perform some operations on a remote server, and the operations cause more than five schema version updates on the data objects.

    For example, you rebuild the index of a table on the remote server to update the schema version of the table on the linked server.

    Note You perform the operations before the next execution of the query.
  • You run the distributed query on the linked server again.

In this scenario, the query is not recompiled, and you receive an error message that resembles the following:
Server: Msg 7359, Level Level Number, State State Number, Line Line Number
The OLE DB provider "Provider Name" for linked server "Linked Server Name" reported a change in schema version between compile time ("Compile Time") and run time ("Run Time") for table "Linked Table Name".
Notes
  • Provider Name is a placeholder for the name of the OLE DB provider.
  • Linked Table Name is a placeholder for the name of the table that is queried on the linked server.
  • The following statements can usually change the schema version:
    • ALTER TABLE
    • CREATE INDEX
    • DROP INDEX
    • DBCC REINDEX

CAUSE

This issue occurs because a recompilation limit for queries is reached.

When a change is made to the schema, some objects in the cache are dropped and the query requires a recompilation operation. However, an upper limit for recompiling is reached after more than five changes that update the schema version are made. Therefore, the issue that is mentioned in the "Symptoms" section occurs.

RESOLUTION

Cumulative update information

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 11. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2633145 Cumulative Update package 11 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2633146 Cumulative Update package 4 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616 The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 3

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 3. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2617146 Cumulative update package 1 for SQL Server 2008 Service Pack 3
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2629969 The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 3 hotfix to an installation of SQL Server 2008 Service Pack 3. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

Cumulative update package 6 for SQL Server 2008 SP2

The fix for this issue was first released in cumulative update package 6. For more information about how to obtain this cumulative update package for SQL Server 2008 SP2, click the following article number to view the article in the Microsoft Knowledge Base:
2582285 Cumulative update package 6 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new update release contains all the hotfixes and all the security updates that were included with the previous SQL Server 2008 SP2 update release. We recommend that you consider applying the most recent update release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659 The SQL Server 2008 builds that were released after SQL Server 2008 SP2 was released



WORKAROUND

To work around this issue, use one of the following methods:
  • Run the DBCC FREEPROCCACHE('Plan_Handle') statement.

    For more information about the Plan_Handle parameter, visit the following MSDN website:
    General information about the Plan_Handle parameter
  • Run the sp_refreshView 'ViewName' stored procedure.

    Note This method does not work if cumulative update package 3 for SQL Server 2008 SP2 is installed.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

Properties

Article ID: 2588970 - Last Review: December 19, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 R2 Datacenter
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
  • Microsoft SQL Server 2008 R2 Express with Advanced Services
  • Microsoft SQL Server 2008 R2 Standard
  • Microsoft SQL Server 2008 R2 Workgroup
  • Microsoft SQL Server 2008 Service Pack 1
  • Microsoft SQL Server 2008 Service Pack 2
  • Microsoft SQL Server 2008 Standard
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2588970

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com