Microsoft KB Archive/945901

= FIX: A query that uses the FOR XML AUTO clause generates different results in SQL Server 2000 and in SQL Server 2005 =

Article ID: 945901

Article Last Modified on 1/3/2008

-

APPLIES TO


 * Microsoft SQL Server 2005 Standard Edition
 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard X64 Edition
 * Microsoft SQL Server 2005 Standard Edition for Itanium-based Systems
 * Microsoft SQL Server 2005 Enterprise X64 Edition
 * Microsoft SQL Server 2005 Enterprise Edition for Itanium-based Systems

-



Bug: #50001958 (SQL Hotfix)



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.



SYMPTOMS
When you run a query that uses the FOR XML AUTO clause in Microsoft SQL Server 2005, the result differs from the result that you receive when you run the same query in SQL Server 2000. This problem occurs if the following conditions are true:  The query uses a conversion function on a column.  In the conversion function, the source column is same as the destination column. For example, the query uses the following conversion function on a column of the datetime data type: cast(ColumnA as datetime) as ColumnB 

Additionally, if you set the database compatibility level of the instance to 80, and then you run the query again, the result is still different from the result in SQL Server 2000.



CAUSE
This issue occurs because the SQL Server 2005 database engine ignores the conversion function when the database engine compares the source column and the destination column when the source column and the destination column are same. However, the SQL Server 2000 database engine does not ignore the conversion function.



RESOLUTION
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 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

943656 Cumulative update package 5 for SQL Server 2005 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 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:

937137 The SQL Server 2005 builds that were released after SQL Server 2005 Service Pack 2 was released

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.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
After you apply this hotfix, you receive a consistent result between SQL Server 2000 and SQL Server 2005 when you set the database compatibility level of the instance to 80 in the scenario that the &quot;Symptoms&quot; section describes.

Steps to reproduce the problem
 Install the Northwind sample database on an instance of SQL Server 2005 and on an instance of SQL Server 2000.  Run the following query in both of the two instances of SQL Server: select top 1 t1.orderid ,t1.customerid ,t2.productid ,t1.shipregion ,cast(t2.unitPrice as money) unitPrice ,cast(t1.OrderDate as datetime) as OrderDate from orders t1 join [order Details] t2 on t1.orderid= t2.orderid where shipregion is not null for xml auto </li></ol>

In the instance of SQL Server 2000, you receive the following result: <t1 orderid=&quot;10283&quot; customerid=&quot;LILAS&quot; shipregion=&quot;Lara&quot;> <t2 productid=&quot;15&quot; unitPrice=&quot;12.4000&quot; OrderDate=&quot;1996-08-16T00:00:00&quot; /> </t1> In the instance of SQL Server 2005, you receive the following result: <t1 orderid=&quot;10250&quot; customerid=&quot;HANAR&quot; shipregion=&quot;RJ&quot; OrderDate=&quot;1996-07-08T00:00:00&quot;> <t2 productid=&quot;41&quot; unitPrice=&quot;7.7000&quot; /> </t1> 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:

943656 Cumulative update package 5 for SQL Server 2005 Service Pack 2

<div class="references_section">