Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Using XPath and XQuery.

From: "Han" <hp4444@------.---.----->
To: NULL
Date: 5/3/2005 9:35:00 PM
That depends on the regularity of the tree.
If it has regular structure, you can seperate each nodes into separate 
records, save them in xml typed fields in sql 2005(now beta), and apply 
indexing against the field. That's not pure XML indexing, but it showed 10 
times faster performance compared with non-indexed ones. Related NG,

http://communities.microsoft.com/newsgroups/default.asp?icp=sqlserver2005&slcid=us&NewsGroup=microsoft.private.sqlserver2005.express

"Sami" <s8a2m9i1_i5s1l9a6m@h...> wrote in message 
news:OG$%23La9TFHA.3392@T......
> Hello,
> Does one need to read the whole XML Document into a DOM object to be able 
> to
> use XPath and/or XQuery to retrieve information from the document.
>
> Is there any other way to retrieve information quickly and efficiently 
> from
> an extremely large XML Document without having to store it first in a DOM
> object?
>
> -- 
> Regards,
> Sami
>
> [Remove Numbers from e-mail address to use it]
>
> 




transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent