Select the product you need help with
FIX: You obtain incorrect values for a column when you use the OPENROWSET function to import data from a data file by using an XML format file in SQL Server 2005 or in SQL Server 2008Article ID: 967206 - View products that this article applies to. Microsoft distributes Microsoft SQL Server 2005 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 2005 fix release. Microsoft distributes Microsoft SQL Server 2008 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 fix release. On This PageSYMPTOMSConsider the following scenario. You create an XML format file in which a <COLUMN> element defines that the column cannot have NULL values. You have a data file that has a NULL value or an empty value for the column. Then, you use the OPENROWSET function to import data from the data file by using the XML format file in Microsoft SQL Server 2005 or in Microsoft SQL Server 2008. In this scenario, you obtain incorrect values for the column. However, you expect to receive an error message because the NULL value or the empty value is not valid. RESOLUTIONCumulative update information for SQL Server 2005 Service Pack 2The fix for this issue was first released in Cumulative Update 13 for SQL Server 2005 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:967908 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 2005 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/967908/LN/
)
Cumulative update package 13 for SQL Server 2005 Service Pack 2937137
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 2 hotfix to an installation of SQL Server 2005 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.
(http://support.microsoft.com/kb/937137/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
Cumulative update information for SQL Server 2005 Service Pack 3The fix for this issue was also released in Cumulative Update 3 for SQL Server 2005 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:967909 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 2005 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/967909/LN/
)
Cumulative update package 3 for SQL Server 2005 Service Pack 3960598
Microsoft SQL Server 2005 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2005 Service Pack 3 hotfix to an installation of SQL Server 2005 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.
(http://support.microsoft.com/kb/960598/LN/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
Cumulative update information for SQL Server 2008The fix for this issue was first released in Cumulative Update 5 for SQL Server 2008. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:969531 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:
(http://support.microsoft.com/kb/969531/
)
Cumulative update package 5 for SQL Server 2008956909
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was releasedCumulative update information for SQL Server 2008 Service Pack 1The fix for this issue was first released in Cumulative Update 2 for SQL Server 2008 Service Pack 1. For more information about how to obtain this cumulative update package for SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:970315 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:
(http://support.microsoft.com/kb/970315/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 1970365
(http://support.microsoft.com/kb/970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was releasedSTATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. MORE INFORMATIONFor more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base: 967908 For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/967908/LN/
)
Cumulative update package 13 for SQL Server 2005 Service Pack 2967909 For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/967909/LN/
)
Cumulative update package 3 for SQL Server 2005 Service Pack 3969531 For more information about what files are changed, and for information about any prerequisites to apply the cumulative update package that contains the hotfix that is described in this Microsoft Knowledge Base article, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/969531/LN/
)
Cumulative update package 5 for SQL Server 2008970315
(http://support.microsoft.com/kb/970315/LN/
)
Cumulative update package 2 for SQL Server 2008 Service Pack 1REFERENCES
For more information about the list of builds that are available after SQL Server 2005 Service Pack 3, click the following article number to view the article in the Microsoft Knowledge Base:
960598
For more information about the list of builds that are available after SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/960598/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 3 was released
937137
For more information about the list of builds that are available after SQL Server 2008, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/937137/
)
The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released
956909
For more information about the list of builds that are available after SQL Server 2008 Service Pack 1, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/956909/
)
The SQL Server 2008 builds that were released after SQL Server 2008 was released
970365
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:
(http://support.microsoft.com/kb/970365/
)
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
935897
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:
(http://support.microsoft.com/kb/935897/
)
An Incremental Servicing Model is available from the SQL Server team to deliver hotfixes for reported problems
822499 For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/822499/
)
New naming schema for Microsoft SQL Server software update packages
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updatesPropertiesArticle ID: 967206 - Last Review: May 18, 2009 - Revision: 2.0 APPLIES TO
|
Back to the top
