Click here to Skip to main content
15,901,035 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Hi,

I have more than 15-20 tables to add/update while doing a single transaction. I also need to maintain the history for each table. What could be the best design pattern for this situvation?

The tables could be different each time.

Regards,
Rakhesh R
Posted
Updated 25-Oct-11 0:55am
v2
Comments
Slacker007 25-Oct-11 6:55am    
Edit: readability and formatting.

1 solution

I would go for a datawarehouse and use a type 2 datawarehouse.
An update will then require you to expire the row to be updated and add a new row to replace the expired row.

Tip:
Datarehousing is a big big area and not to be contemplated without a thorough investigation first!
 
Share this answer
 
Comments
Rakhesh Rajan 25-Oct-11 8:06am    
Is there any design pattern helpful for this situation? Mine is an asp.net application, where only in one page i have to capture the details to 15-20 tables and monitor the history.Rest all pages are one to one.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900