Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
24/7 Data Warehoue and load strategy
- Thread starter goodmans
- Start date
johnherman
MIS
If the underlying database is RDBMS, you would load using a single transaction so that all new activity hits at once, with a single commit at the end of the transaction. You could also have a control table which contained the date/time of the last update.
Another method would be to use replication or some variation of replication from the source system(s) to the target systems. But again, you would want to maintain the integrity of a transaction. If someone was transferring $100 from checking to savings, you wouldn't want to post the withdrawal from checking without also providing commit to the deposit into savings.
-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright
Another method would be to use replication or some variation of replication from the source system(s) to the target systems. But again, you would want to maintain the integrity of a transaction. If someone was transferring $100 from checking to savings, you wouldn't want to post the withdrawal from checking without also providing commit to the deposit into savings.
-------------------------
The trouble with doing something right the first time is that nobody appreciates how difficult it was - Steven Wright
- Thread starter
- #4
- Thread starter
- #5
- Status
Similar threads
- Locked
- Question
- Locked
- Question