Hi Dana,


Here's SAX definition from MSDN:

Simple API for XML (SAX)

An XML API that allows developers to take advantage of event-driven XML parsing. Unlike the DOM specification, SAX doesn't require the entire XML file to be loaded into memory. SAX notifies you when certain events happen as it parses your document. When you respond to an event, any data you don't specifically store is discarded. If your document is very large, using SAX will save significant amounts of memory when compared to using DOM. This is especially true if you only need a few elements in a large document.


Take a look also at http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnmsxml/html/sax2jumpstart.asp

>Sergey, Hi. What is SAX? Is it a library, or a third party tool?
>I find XML to be very slow if there is a large chunk of data. XMLTOCURSOR works OK for small datasets, but on a large file it is like watching grass grow.
>
>I had to create some data imports via XML. I tried XMLTOCURSOR and timed it. It ran for two hours and was not done, and there was no way of telling how much longer it would be. Then I wrote a parsing program using low level routines [FOPEN(), FGETS()]. The same amount of data takes six minutes to import in this manor. We're talking about more than a quarter million records, even though the record length isn't that long. I forget how, but I had estimated that the XMLTOCURSOR() route would have taken upwards of five hours. Let's see...five hours, six minute...five hours, six minutes...three times a day. FOPEN() wins!
>