Select the product you need help with
FIX: Incorrect results when the SqlConnection.GetSchema method retrieves a table’s schema information in SQL Server 2008, in SQL Server 2008 R2 or in SQL Server 2012Article ID: 2658474 On This PageMicrosoft distributes Microsoft SQL Server 2008 Service Pack 3 (SP3), Microsoft SQL Server 2008 R2 or Microsoft SQL Server 2012 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 Service Pack 3 (SP3), SQL Server 2008 R2 or SQL Server 2012 fix release. SymptomsAssume that you have a client application that uses the SqlConnection.GetSchema method to retrieve a table’s schema information. This table includes a column name that contains a period (.). For example, one of the column names in the table is "Column1.A." In this situation, the column whose name contains a period is missing from the results that the SqlConnection.GetSchema method returns. Note This issue does not occur when you use the OleDbConnection.GetSchema method. CauseTo evaluate the permissions for columns, SQL Server 2008 Service Pack 1 uses the HAS_PERMS_BY_NAME function instead of the PERMISSIONS function in the sys.spt_columns_view_managed system view. However, if a column name contains a period and is not included in the QUOTENAME function, the HAS_PERMS_BY_NAME function considers the user to have insufficient permissions for that column. Therefore, the issue that is mentioned in the "Symptoms" section occurs. ResolutionCumulative update informationSQL Server 2008 R2 Service Pack 2The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 2. 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:2720425 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:
(http://support.microsoft.com/kb/2720425/
)
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 22730301
(http://support.microsoft.com/kb/2730301/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 2 was released SQL Server 2012The fix for this issue was first released in Cumulative Update 2 for SQL Server 2012. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:2703275 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 2012 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:
(http://support.microsoft.com/kb/2703275/LN/
)
Cumulative update package 2 for SQL Server 20122692828 You must apply a SQL Server 2012 hotfix to an installation of SQL Server 2012.
(http://support.microsoft.com/kb/2692828/LN/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 7 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:2703282 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:
(http://support.microsoft.com/kb/2703282/
)
Cumulative Update package 7 for SQL Server 2008 R2 Service Pack 12567616
(http://support.microsoft.com/kb/2567616/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released SQL Server 2008 R2The fix for this issue was first released in Cumulative Update 13. 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:2679366 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:
(http://support.microsoft.com/kb/2679366/
)
Cumulative Update package 13 for SQL Server 2008 R2 981356
(http://support.microsoft.com/kb/981356/
)
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was releasedCumulative update package 4 for SQL Server 2008 SP3The fix for this issue was first released in Cumulative Update 4. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 4, click the following article number to view the article in the Microsoft Knowledge Base:2673383 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 Service Pack 4 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:
(http://support.microsoft.com/kb/2673383/
)
Cumulative update package 4 for SQL Server 2008 Service Pack 32629969
(http://support.microsoft.com/kb/2629969/
)
SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was releasedMore informationFor more information about the SqlConnection.GetSchema method, visit the following MSDN website: General information about the SqlConnection.GetSchema method
(http://msdn.microsoft.com/en-us/library/ms136365.aspx)
StatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2658474 - Last Review: November 21, 2012 - Revision: 6.1
| Article Translations
 |
Back to the top
