Log on:
Powered by Elgg

Cuong Nguyen :: Blog :: Mapping XML documents and relational data will be challenging in the integration process and the other issues based on my past experience

July 06, 2007

default user icon
Cuong Nguyen

Mapping XML documents and relational data will be challenging in the integration process and the other issues based on my past experience
  • Currently /5

Avg rating: - - based on 0 ratings

5 Stars 0
4 Stars 0
3 Stars 0
2 Stars 0
1 Star 0
   * Includes your rating
--(Log in to rate this blog post!)--

Last year, while I was working at one project at a company in Irvine, I had to use the XMLspy tool to help me to complete the task. Even the tool is very useful but I felt uneasy while I had to design new tables and wrote new functions to support new requirements because the structure of data was stored different. It takes time to get use with it.Most developers felt the same way when they first started to write code for web-based application using XML databases instead of relational database. We also might run into problem if we try to overuse it. We might end up with the system with many XML files for business rules, system configuration, and XSD schema integration. Then when we want to deploy a new application or new release for a specific business, the person wrote a new set up program to install the package of software have to know exactly what kind of business rule files, configuration files to go together with different release. The packaging job for a new or incremental release will be more painful and it will be easy to make a mistake.The performance of the whole system will be very slow if you have to search value from XML files or using Xquery for a large set of database. Even in the book the author suggest using native XML database to improve the retrieval process, it will not help much for a large data set if the data is updating more frequently. 

 

Keywords: Relational data, XML documents

Posted by Cuong Nguyen

You must be logged in to post a comment.