When you run a linked server query from one instance of Microsoft SQL Server 2008 or SQL Server 2008 R2 to another instance of SQL Server, the query fails, and you receive an error message that resembles the following:
Msg 8180, Level 16, State 1, Line 1
Statement(s) could not be prepared.
Msg 4104, Level 16, State 1, Line 1
The multi-part identifier "<column name>" could not be bound.
Msg 207, Level 16, State 1, Line 1
Invalid column name '<column name>'.
This issue occurs because some columns are incorrectly included in the linked server query. However, these columns are not in the linked server table. Therefore, the query fails.
Note To display information about each statement of the linked server query, use the
SET SHOWPLAN_ALL or
SET SHOWPLAN_XML setting. To determine whether the query is incorrectly formed, check the
Remote Query section of the
SET SHOWPLAN_ALL or
SET SHOWPLAN_XML setting output.
SQL Server 2008 Service Pack 1
The fix for this issue was first released in Cumulative Update 10 for SQL Server 2008 Service Pack 1. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2279604
(http://kbalertz.com/Feedback.aspx?kbNumber=2279604/
)
Cumulative update package 10 for SQL Server 2008 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 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:
970365
(http://kbalertz.com/Feedback.aspx?kbNumber=970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 1 hotfix to an installation of SQL Server 2008 Service Pack 1. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
SQL Server 2008 Service Pack 2
The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2289254
(http://kbalertz.com/Feedback.aspx?kbNumber=2289254/
)
Cumulative update 1 for SQL Server 2008 Service Pack 2
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. 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:
2402659
(http://kbalertz.com/Feedback.aspx?kbNumber=2402659]/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
SQL Server 2008 R2
The fix for this issue was first released in Cumulative Update 5. 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:
2438347
(http://kbalertz.com/Feedback.aspx?kbNumber=2438347/
)
Cumulative Update package 5 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
(http://kbalertz.com/Feedback.aspx?kbNumber=981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released
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
SET SHOWPLAN_XML setting, visit the following Microsoft Developer Network (MSDN) website:
For more information about the
SET SHOWPLAN_ALL setting, visit the following MSDN website:
For more information about the Incremental Servicing Model for SQL Server, click the following article number to view the article in the Microsoft Knowledge Base:
935897
(http://kbalertz.com/Feedback.aspx?kbNumber=935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
For more information about the naming schema for SQL Server updates, click the following article number to view the article in the Microsoft Knowledge Base:
822499
(http://kbalertz.com/Feedback.aspx?kbNumber=822499/
)
New naming schema for Microsoft SQL Server software update packages
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://kbalertz.com/Feedback.aspx?kbNumber=824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 2352413 - Last Review: December 23, 2010 - Revision: 3.0
APPLIES TO
- Microsoft SQL Server 2008 Enterprise
- Microsoft SQL Server 2008 Developer
- Microsoft SQL Server 2008 Standard
- Microsoft SQL Server 2008 Standard Edition for Small Business
- Microsoft SQL Server 2008 Workgroup
- Microsoft SQL Server 2008 R2 Developer
- Microsoft SQL Server 2008 R2 Enterprise
- Microsoft SQL Server 2008 R2 Standard
- Microsoft SQL Server 2008 R2 Workgroup
| kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2352413 |