Microsoft KB Archive/933808

= FIX: Error message when you run a query that contains nested FOR XML clauses in SQL Server 2005: “The XML data type is damaged” =

Article ID: 933808

Article Last Modified on 11/20/2007

-

APPLIES TO


 * Microsoft SQL Server 2005 Developer Edition
 * Microsoft SQL Server 2005 Enterprise Edition
 * Microsoft SQL Server 2005 Standard 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
 * Microsoft SQL Server 2005 Workgroup Edition

-



Bug: #50000918 (SQL Hotfix)



Notice
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.



SUMMARY
This article describes the following about this hotfix release:
 * The issues that are fixed by the hotfix package
 * The prerequisites for installing the hotfix package
 * Whether you must restart the computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes
 * The files that are contained in the hotfix package



SYMPTOMS
When you run a query that contains nested FOR XML clauses in SQL Server 2005, you receive the following error message:

Msg 6611, Level 16, State 1, Line 2

The XML data type is damaged.

This problem occurs if the following conditions are true:
 * The FOR XML clauses use the TYPE directive.
 * You specify an XQuery query against the XML data type that is returned by the query.
 * In the XQuery query, you reference the QNames in the top of the FOR XML clause.



Cumulative update information
To resolve this problem, obtain the cumulative update package for SQL Server 2005 Service Pack 2 (build 3161). For more information about how to obtain the cumulative update package (build 3161), click the following article number to view the article in the Microsoft Knowledge Base:

935356 Cumulative update package (build 3161) for SQL Server 2005 Service Pack 2 is available

Hotfix information
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
 SQL Server 2005 Service Pack 2

For more information about how to obtain SQL Server 2005 Service Pack 2, click the following article number to view the article in the Microsoft Knowledge Base:

913089 How to obtain the latest service pack for SQL Server 2005



Restart information
You do not have to restart the computer after you apply this hotfix.

Registry information
You do not have to change the registry.

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build. The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

SQL Server 2005 Itanium architecture version


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
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 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 Description of the standard terminology that is used to describe Microsoft software updates

Steps to reproduce the problem
 Open SQL Server Management Studio, and then create a new query.  Run the following statements: CREATE TABLE [dbo].[TABLE0](   [COL0] [int] NULL,    [COL1] [varchar](50) NULL,    [COL2] [varchar](50) NULL,    [COL3] [varchar](50) NULL,    [COL4] [varchar](50) NULL,    [COL5] [varchar](50) NULL,    [COL6] [varchar](50) NULL,    [COL7] [varchar](50) NULL,    [COL8] [varchar](50) NULL ) ON [PRIMARY]

CREATE TABLE [dbo].[TABLE1](   [COL0] [int] NULL,    [COL1] [int] NULL,    [COL2] [varchar](50) NULL,    [COL3] [varchar](50) NULL,    [COL4] [varchar](50) NULL,    [COL5] [varchar](50) NULL,    [COL6] [varchar](50) NULL,    [COL7] [varchar](50) NULL,    [COL8] [varchar](50) NULL ) ON [PRIMARY] GO

-- Populating tables

DECLARE @X INT, @Y INT SET @X=0 WHILE @X < 20 BEGIN INSERT TABLE0 VALUES(@X,'DATAFORCOLUMN1','DATAFORCOLUMN2','DATAFORCOLUMN3','DATAFORCOLUMN4','DATAFORCOLUMN5','DATAFORCOLUMN6','DATAFORCOLUMN7','DATAFORCOLUMN8') SET @Y=0 WHILE @Y < 20 BEGIN INSERT TABLE1 VALUES(@X,@Y,'DATAFORCOLUMN2','DATAFORCOLUMN3','DATAFORCOLUMN4','DATAFORCOLUMN5','DATAFORCOLUMN6','DATAFORCOLUMN7','DATAFORCOLUMN8') SET @Y=@Y+1 END SET @X=@X+1 END

--

SELECT (    SELECT TABLE0.COL0,            TABLE0.COL1,            TABLE0.COL2,            TABLE0.COL3,            TABLE0.COL4,            TABLE0.COL5,            TABLE0.COL6,            TABLE0.COL7,            TABLE0.COL8,            ( SELECT TABLE1.COL0, TABLE1.COL1, TABLE1.COL2, TABLE1.COL3, TABLE1.COL4, TABLE1.COL5, TABLE1.COL6, TABLE1.COL7, TABLE1.COL8 FROM TABLE1 WHERE TABLE0.COL0=TABLE1.COL0 FOR XML PATH('RECORDS'), ROOT('TABLE1'),TYPE )      FROM            TABLE0 FOR XML PATH('RECORDS'), ROOT('TABLE0'),TYPE         ).query ('     for $record in /TABLE0/RECORDS/TABLE1/RECORDS      return                              {$record/../../COL0}                  {$record/COL1}            </OUTPUTXML> ') </li></ol>

Keywords: kbfix kbqfe kbpubtypekc kbexpertiseadvanced kbhotfixserver kbsql2005engine KB933808

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.