Altova Mailing List Archives

RE: [xml-dev] XML storage

From: "Michael Kay" <michael.h.kay@--------.--->
To: "'Helena'" <helenaforsberg@----.-->,<xml-dev@-----.---.--->
Date: 8/29/2003 2:27:00 PM
> I want to store a large number (somewhere around 50000) of 
> data-centric XML documents. I'm a total newbie at this, but a 
> little research has revealed that there is three main ways to 
> go, store them as BLOBs in a RDBMS, map them up into 
> relations, or use a native database. The documents will all 
> conform to the same DTD, and will vary in size between 9 and 
> 50 KB. The DTD contains many optional elements, no mixed 
> contents, no processing instructions, CDATA or comments. The 
> structure is not really important to preserve, and there is 
> no need for full-text querying. However, I'm afraid the 
> relational approach will result in too many relations for 
> efficient querying. The DTD contains 225 elements. 

This sounds like a very good fit to the kind of things which a Native
XML database like Tamino is designed to handle.

The problems with the RDBMS approach is that typically you either have
to shred the document into tiny pieces, which gives you an
incomprehensibly complex database and a lot of cost on storage and
retrieval, or you store a raw CLOB, in which case you are getting very
little value out of the ability of a database to store structured data.
There are cases where storing XML in relational databases makes sense
(like when you've got one handy and don't want to get another) but this
looks to me like a Native XML scenario. I'm biased, of course.

Michael Kay
Software AG


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 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.