It looks like this could be placed in a number of different forums but since I'm working with XML I'll try here.

Okay, I'm working with a legacy classic asp application that either displays data in graphs or tables. For the graphs we use a graphing component that likes XML and since we already have the XML, we use xslt to display the data in a table if that is the users preference. The graphs work well regardless of the amount of data returned in the XML. With the tables, we do some pagination so those load well also. The area we have a problem is if the user want to generate csv file from the XML data.

In this case we are passing the xml to a DLL that parses the xml using the XML DOM and when done sends it to the browser. If there are a large number of records in the XML file the script times out before the processing completes.

As stated above, we are using the XML DOM for processing right now. Would we realize any performance gains by switching to SAX or would gathering our data into a recordset and parsing the recordset be any quicker?

I have never used SAX but from the quick research I have done, I'm not sure it is the way to go since I will be using every element in the xml when generating the csv files.