RE: why xml, why not use ado recordsets

Greg,

There are three common ways to construct the xml with SQL,ADO,IIS;
1. Use ADO recordsets created from regular select or stored proc, loop thru
using DOM model and VB/ASP code to create XML file or variable.
2. Select from SQLServer using 'for xml' syntax in select statement to
create XML string.
3. Use Save method in AdPersistXML from the ADO recordset.

Here are my experiences (opinions)
Method 1.
	advantages;
	disadvantages;
		- Slow speed of loops and DOM model use to build XML
(particularly
		if in ASP code)
		- Hard to maintain when changing database tables

Method 2. (I haven't used this method yet)
	advantages;
		- Performance 
		- Control over xml structure
	disadvantages;
		- Tied to SQL Server and particular versions that support
'for xml'
	
Method 3.
	advantages;
		- Small code footprint to create xml 
		- Change to database table requires no change to vb/asp code
(
		may need xsl change)
		- Performance advantage just create recordset then save to 
		file or variable
	disadvantages;
		- Little or no control over xml structure (could use a
utility xsl 
		file to format nicely before converting to html)

Regards,
Ben

-----Original Message-----
From: Greg Fichter [mailto:gfichter@xxxxxxxxxxxxxxxxxx]
Sent: 26 July 2002 00:42
To: XSL-List@xxxxxxxxxxxxxxxxxxxxxx
Subject:  why xml, why not use ado recordsets


Why use xml as the data exchange between SQL server and Internet Information
server.  Why not just use ADO recordsets?


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
=====================================================================
DISCLAIMER

1. The information contained in this E-mail is confidential. 
   It is intended only for the stated addressee(s) and access 
   to it by any other person is unauthorised. 
   If you are not an addressee, you must not disclose, copy, 
   circulate or in any other way use or rely on the information 
   contained in this E-mail. Such unauthorised use may be unlawful. 
   If you have received this E-mail in error, please inform us 
   immediately and delete it and all copies from your system.

2. The views expressed in this E-mail are those of the author, 
    and do not represent the views of AMT-Sybex Group Ltd., its 
    associates or subsidiaries, unless otherwise expressly indicated.
    In the avoidance of doubt, the insertion of the name of AMT-Sybex 
    Group Ltd., its associate or subsidiary under the name of the sender 
    may constitute an express indication that the views stated in the Mail 
    are those of the named company.
=====================================================================
For more information on the AMT Sybex group visit: http://www.amt-sybex.com 



 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list