When introducing SQL2k before, I mentioned SQL2k's support for XML. Using the for XML statement, you can easily convert the execution result into an XML, which can greatly improve the system's operating efficiency and development speed. Detailed Please see Books Online for content.
But the way of accessing the returned XML using ADO (Required ADO 2.6) is different from the original Recordset. If you still use Recordset to access, you can only get an XML Schema in Unicode format, but not the XML content.
In fact, this problem can be solved easily, but I thought I was very familiar with ADO and didn't look at Help carefully, so I didn't find that ADO uses Stream to get and return XML.
The Command object has two properties, called Input Stream and Output Stream. The value of the property is an IUnknown interface. You can assign an XML Parser interface to it, or use Request, Response, etc. directly. The advantage of this is that there is no need to generate a Recordset or save the data, thus saving system overhead.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
