OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: storing xml files into database

> Haresh:
> Since I work for a native XML database company, you might not 
> consider my advice to be valid... but I'm going to give it anyways ;->
> I have customer story after customer story where the first 
> thing they tried was Oracle or DB2 or SQL Server for storing 
> their XML. It was a natural thing for them to try as they 
> already had those products installed. They came to eXcelon 
> primarily because they failed at making an RDBMS handle XML 
> in a way that was useful. One of our customers, for example, 
> had Oracle consultants create a benchmark on Oracle 9i 
> against our consultants using eXcelon. Oracle was unable to 
> complete the benchmark and we won the deal... and these were 
> top-notch Oracle consultants.
> A couple of questions that will quickly let you know that an 
> RDBMS is not going to work:
> 1) Are you dealing with XML data whose schema is not 
> necessarily consistent from document to document or the 
> schemas change often? The key advantage of using XML as a 
> data model is extensibility: you lose that advantage when you 
> store it in an RDBMS.

How do you loose the advantage.  No really, I am not trying to be sarcastic,
but you sound like a good
sales person without actually explaining the anwer.  Really, I'd like to

> 2) Do you need to update this data often? All current RDBMS 
> implementations (except for a beta utility available for 
> Microsoft for SQL Server) do not allow incremental document 
> updates. You must replace entire documents when you need to 
> make a change as all of the RDBMS systems store the data as 
> BLOBs. Most of our competitors in the XML DB world also do 
> not allow incremental updates. This is very important should 
> data need to change fairly often.

When do you not have to read through the whole document to change anything,
weather it's XML of flat data file.  Again, some technical expetise would
definitelly help this case.  Again, I am not doubting you, but rather am
very interested in this approach of not reading in a document to make a
change.  Yes, externally it might not seem that way, but internally?

> 3) Is performance and scalability important to you? We've 
> tried both Oracle and DB2 with over 100,000 documents, which 
> is a relatively small amount. Oracle fails the benchmark, and 

Why does Oracle fail?  At what point does it choke?