File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
The moose likes XML and Related Technologies and the fly likes XML over Relational Data Storage Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login
JavaRanch » Java Forums » Engineering » XML and Related Technologies
Bookmark "XML over Relational Data Storage" Watch "XML over Relational Data Storage" New topic

XML over Relational Data Storage

chetak faldesai

Joined: Jun 11, 2003
Posts: 28
I am in process of designing a database to hold archival data. The data is read only. No updates need to be made at any time.
Entire details about a particular records spans across 10 to 12 rows in the database, if i go for relational approach.
I need to display data for that entire record as part of display mechanism.
The frequency of data to be retrieved is very less. maybe once in 4 months or so.

First Approach:
Since the data is read only I figured that the entire data for a record can also be placed in a big table. Ideally that is something we always avoid, but since it is just read and display, if indexing is done properly, it should be ok right?

Second approach:
put the entire record data in a xml file and save in the database as a blob.
Use tools such as Db2 XML Extender for retreiving the data.

which of the two approaches should i go for. Are there any disadvantages in using second approach in terms of performances?
Are there any advantages of second approach in terms of Database space(blob is compressed right?)
I am quite new at this and will appreciate help.
I agree. Here's the link:
subject: XML over Relational Data Storage
It's not a secret anymore!