The CommandText property ordinarily specifies a Transact-SQL statement with a valid FOR XML clause. However, CommandText can also specify a statement that returns ntext or nvarchar data that contains valid XML, or the contents of a column defined with the xml data type.
A typical ExecuteXmlReader query can be formatted as in the following Microsoft Visual C# example:
SqlCommand command = new SqlCommand("SELECT * FROM dbo.Customers FOR XML AUTO, XMLDATA", SqlConn);
Note: |
|---|
This type of query only works with Microsoft SQL Server 2000 or later. For more information see Guidelines for Using the FOR XML Clause in SQL Server Books Online. |
When used with SQL Server 2005, this method can also be used to retrieve a single-row, single-column result set that contains XML data. In this case, if more than one row is returned, the ExecuteXmlReader method attaches the XmlReader to the value on the first row, and discards the rest of the result set.
When you use versions of SQL Server earlier than SQL Server 2005, while the XmlReader is being used the associated SqlConnection is busy serving the XmlReader. While in this state, no other operations can be performed on the SqlConnection other than closing it. This is the case until the Close method of the XmlReader is called. Starting with SQL Server 2005, the multiple active result set (MARS) feature allows for multiple actions using the same connection.
If you use ExecuteReader or BeginExecuteReader to access XML data, SQL Server will return any XML results greater than 2,033 characters in length in multiple rows of 2,033 characters each. To avoid this behavior, use ExecuteXmlReader or BeginExecuteXmlReader to read FOR XML queries. For more information, see article Q310378, "PRB: XML Data Is Truncated When You Use SqlDataReader," in the Microsoft Knowledge Base at http://support.microsoft.com.