10 Reasons why DBAs Should Use Native XML Conor O’Mahony [email_address]

Intro Native XML storage is often the best option However, sometimes shredding or LOB storage are better Here are some reasons to use native XML storage Some of them may apply to you

Native XML storage is often the best option

However, sometimes shredding or LOB storage are better

Here are some reasons to use native XML storage

Some of them may apply to you

1 Learn Valuable New XML Skills XML is rapidly gaining adoption XML ubiquity for certain information is inevitable Knowing the optimal ways to store XML is a valuable skill

XML is rapidly gaining adoption

XML ubiquity for certain information is inevitable

Knowing the optimal ways to store XML is a valuable skill

Reduce Server Load for Queries Against XML Data 2 www.ibm.com/developerworks/db2/ library/techarticle/dm-0612nicola/ For XML data, queries are often faster when XML is stored in native form For details, see:

Reduce Server Load for Queries Against XML Data

For XML data, queries are often faster when XML is stored in native form

For details, see:

3 www.ibm.com/developerworks/db2/ library/techarticle/dm-0612nicola/ For shredding, the server must do more work when inserting XML data. For more information, see: Reduce Server Load During Insert of XML Data

For shredding, the server must do more work when inserting XML data.

For more information, see:

4 Native XML storage format is typically optimized for XML. Shredding often requires you to store additional copy of XML in CLOB to meet compliance needs More Efficient Storage

Native XML storage format is typically optimized for XML.

Shredding often requires you to store additional copy of XML in CLOB to meet compliance needs

5 Eliminate Relational Mapping for XML Data If shredding, mapping to relational is cumbersome Maintaining the extra relational fields is cumbersome If updating schemas, need to update the mappings. Ugh!

If shredding, mapping to relational is cumbersome

Maintaining the extra relational fields is cumbersome

If updating schemas, need to update the mappings. Ugh!

6 Easier Interactions with Development Provide them with simpler data insert commands, when compared with shredding Provide them with simpler query commands

Provide them with simpler data insert commands, when compared with shredding

Provide them with simpler query commands

7 Provide Better Interface for Querying XML Data Use query languages specially designed for working with XML data: SQL/XML or XQuery More expressive, powerful, and efficient

Use query languages specially designed for working with XML data: SQL/XML or XQuery

More expressive, powerful, and efficient

8 Optimize Schema Usage Use the best schema XML schemas for XML data Relational schemas for relational data

Use the best schema

XML schemas for XML data

Relational schemas for relational data

9 Easier Updates for XML Data Quick and easy updates Avoid costly LOB scenario of retrieving, parsing, updating, and storing

Quick and easy updates

Avoid costly LOB scenario of retrieving, parsing, updating, and storing

10 XML for Data with Frequent Schema Changes XML is ideal for data whose format frequently changes XML schemas are more flexible XML data is more flexible

XML is ideal for data whose format frequently changes

XML schemas are more flexible

XML data is more flexible