Select the product you need help with
Support for the varchar(max), nvarchar(max), and varbinary(max) data types is added in most OLE DB providers in SQL Server 2012 or in SQL Server 2008 or in SQL Server 2008 R2Article ID: 2761934 - View products that this article applies to. On This PageIntroductionThis article introduces an update that adds support for the varchar(max), nvarchar(max), and varbinary(max) data types in most OLE DB providers in Microsoft SQL Server 2012, in Microsoft SQL Server 2008 or in Microsoft SQL Server 2008 R2. Note The following OLE DB providers do not support the varchar(max), nvarchar(max), and varbinary(max) data types:
More informationCumulative update informationCumulative Update 2 for SQL Server 2012 SP1The fix for this issue was first released in Cumulative Update 2. For more information about how to obtain this cumulative update package for SQL Server 2012 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2790947 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 SP1 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/2790947/
)
Cumulative update package 2 for SQL Server 2012
Service Pack 12772858
(http://support.microsoft.com/kb/2772858/
)
The SQL
Server 2012 builds that were released after SQL Server 2012 Service Pack 1 was
releasedCumulative Update 5 for SQL Server 2012The 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 2012, click the following article number to view the article in the Microsoft Knowledge Base:2777772 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. 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/2777772/
)
Cumulative update package 5 for SQL Server 2012
2692828
(http://support.microsoft.com/kb/2692828/
)
The SQL Server 2012 builds that were released after SQL Server 2012 was released
Cumulative Update 4 for SQL Server 2008 R2 SP2The 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 R2 SP 2, click the following article number to view the article in the Microsoft Knowledge Base:2777358 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 SP 2 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/2777358/
)
Cumulative update package 4 for SQL Server 2008 R2 Service Pack 2
2730301
(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
Cumulative update package 10 for SQL Server 2008 R2 Service Pack 1The fix for this issue was first released in Cumulative Update 10. For more information about how to obtain this cumulative update package for SQL Server 2008 R2 SP1, click the following article number to view the article in the Microsoft Knowledge Base:2783135 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 SP1 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/2783135/
)
Cumulative update package 10 for SQL Server 2008 R2 SP1
2567616
(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
Cumulative update 8 for SQL Server 2008 Service Pack 3 (SP3)The fix for this issue was first released in Cumulative Update 8. For more information about how to obtain this cumulative update package for SQL Server 2008 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:2771833 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 3 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/2771833/
)
Cumulative update package 8 for SQL Server 2008 Service Pack 32629969
(http://support.microsoft.com/kb/2629969/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 3 was releasedStatusMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. PropertiesArticle ID: 2761934 - Last Review: January 24, 2013 - Revision: 5.0 Applies to
| Article Translations
 |
Back to the top
