Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Designing XML Schemas for use in Oracle 10 - flatter is better or nested is better?

From: "Costello, Roger L." <costello@-----.--->
To: <xmlschema-dev@--.--->, "Costello, Roger L." <costello@-----.--->
Date: 5/16/2006 11:23:00 AM
Hi Folks,

 

Suppose that you are designing an XML Schema for use in an Oracle 10
database.  

 

Does the fact that the Schema is being used in Oracle 10 influence how
you design the Schema?  

 

A colleague told me that, in Oracle 10, queries on data that is
structured in a flat fashion are faster than queries on data that is
structured in a nested (hierarchical) fashion.  "Therefore, we must
design our XML Schemas to structure the data in a flat fashion."  

 

Is my colleague correct - in Oracle 10 queries are faster on flat data
than nested data?

 

I hate to be forced into making Schema design decisions based on the
limitations of the tool being used.  However, we are using Oracle 10,
and if performance is poor on data that is hierarchical then I must be
practical and structure the data in a flat fashion. 

 

Does anyone have experience with designing XML Schemas for use in
Oracle 10?  What's your recommendation - flat or nested?   /Roger

 



transparent
Print
Mail
Digg
delicious
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