I have mentioned SQL2k's support for XML when introducing SQL2k. Using the for XML statement, you can easily convert the execution result into an XML, this greatly improves the system running efficiency and development speed. For details, see Books Online.
However, the method for accessing the returned XML using ADO (Required ADO 2.6) is different from that of the original Recordset. If you still use Recordset for access, you can only get XML Schema in Unicode format, but cannot get XML content.
In fact, this problem can be easily solved, but I thought I was familiar with ADO and did not look at Help carefully, so I did not find that ADO uses Stream to get and return XML.
The Command object has two attributes: Input Stream and Output Stream. The attribute value is an IUnknown interface. You can assign an XML Parser interface to it, or directly use Request and Response. The advantage is that you do not need to generate a Recordset, and you do not need to save the data, thus saving the system overhead.