Re: XQuery vs OpenRowset
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Wed, 5 Apr 2006 22:08:20 +0000 (UTC)
Shilpa (shilpa.nagavara@xxxxxxxxxx) writes:
Please let me know the advantages and disadvantages of XQuery vs
OpenRowSet in SQL Server 2005. Which would be better?
I'm by no means an expert on XML, but I would say that XQuery is
preferrable for all new code that you write. It may not be worth
to rewrite legacy code just for the sake of it.
A major advantage is that you don't need this sp_xml_preparedocument
with XQuery.
Of course, if all you want to do is to unpack an XML document, using
nodes() and CROSS APPLY may feel bulkier, at least initially when the
new syntax may feel akward. Then again, XQuery permits you to do a
lot more things that OPENXML does not, so that you can query an XML
document withour shredding it.
There is one situation you will have to stick to OPENXML, and that is
if you for for some reason are running with any of the options
QUOTED_IDENTIFIER, ANSI_NULLS, ANSI_WARINGS, ANSI_PADDING or
CONCAT_NULL_YIELDS_NULL off. They must be on for XQuery. Note that some
of these options are sticky with stored procedures or table columns.
--
Erland Sommarskog, SQL Server MVP, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- References:
- XQuery vs OpenRowset
- From: Shilpa
- XQuery vs OpenRowset
- Prev by Date: Re: Calculate time lapse
- Next by Date: SQL 2005 Management Studio Bugs
- Previous by thread: XQuery vs OpenRowset
- Next by thread: Problem concatenating column values into string...
- Index(es):
Relevant Pages
|
