This is the mail archive of the xsl-list@mulberrytech.com mailing list .


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

RE: Importing from database


XSLT does not allow for ODBC calls out... you have to pass in a tree
representation of a valid XML document, and process that according to
the XSLT.

There are lots of approaches for integrating with a SQL server:

1) The heavy duty approach - build COM objects to marshall the calls to
the db, and return strings of well formed XML.

2) The lightweight approach - use ASP to build an XML string dynamically
(either through a while not loop or by using ADO recordset's return as
XML feature).

3) Use SQL-XML to build templates of XML, and use the MSXML3
SERVERXMLHTTP method to get the result. [assuming you are using SQL
2000, or SQL 7.0 with the extension].

All of these ways work, and there isn't much in it (SQL-XML is faster,
but unless you are doing really complicated SQL calls, it is barely
noticeable).

Hope that helps,

Ben

> -----Original Message-----
> From: Gustaf Liljegren [mailto:gustaf.liljegren@xml.se]
> Sent: 27 June 2001 10:22
> To: XSL List
> Subject: [xsl] Importing from database
> 
> 
> Hello,
> 
> I have some data in an MS SQL Server database that I'd like 
> to publish on
> paper using XSL, so I wonder if there are any good rules for 
> how to achieve
> this. I know about the export XML functionality in SQL 
> Server, but I figured
> that maybe this step isn't necessary. As the data is filtered through
> XSLT later, maybe there's a way to do the connection between 
> the database
> and XSLT directly, perhaps with extensions?
> 
> Regards,
> 
> Gustaf Liljegren
> 
> 
> 
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
> 
> 

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]