December 24, 2010 at 1:05 am
am developing db 4 insurance association. the db will enable member upload the transaction.
now a policy contain unique like policyno,effectivedate, expirydate, category
where category are motor, marine properties,etc
each category has different schema. eg motror store engineno,chasis no e.t.c. while marine store shiptype e.tc
the system will be used mainly 4 verification say by engineno and it return whether the car is insured with the detail.it will also give some statististal information like noof policy by category.
what will be the best db design
1) store the category information as xml
2)create seperate table for each category
3) any other idea
December 24, 2010 at 2:40 am
I will answer your question by telling you what we did in our database with XML data...
When we stored and queried XML documents in the database, we found querying to be very slow. We did not have a XML index on the table, so that might be the cause of the slow speed. So if you want to query the xml in a table, I suggest reading up on XML indexes.
In the end we went for storing the XML (Hey you might need it sometime for other info! - We did!) but when we inserted/updated the xml we ripped out all the info we query a lot and put that in a table. This worked very well for us!
I do not have a strong opinion on one table for all or multiple tables - one for each category. It depends on the amout of similarity between the category info and if you would ever want to query all the categories at the same time.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply