Article ID: 2615425 - View products that this article applies to.
Consider the following scenario:
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.
This issue occurs because after the schema version of the linked table is changed, the view that uses the linked table is incorrectly recompiled.
SQL Server 2005
Hotfix informationA supported hotfix is now available from Microsoft. However, it is intended to correct only the problem that this article describes. Apply it only to systems that are experiencing this specific problem.
To resolve this problem, contact Microsoft Customer Support Services to obtain the hotfix. For a complete list of Microsoft Customer Support Services telephone numbers and information about support costs, visit the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
PrerequisitesTo apply this hotfix, you must have SQL Server 2005 SP4 installed.
Restart requirementYou may have to restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
To work around this issue, use one of the following methods.
Use the Sqlcmd.exe utility or Microsoft SQL Server Management Studio to run the following statement:
Change the view that uses another view to an equivalent view that does not use another view.
For example, assume that you run the following statements to create two views:
In this scenario, you can run the following statement to create an equivalent OuterView view that does not use the InnerView view:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2615425 - Last Review: October 24, 2011 - Revision: 2.0