|
There are two reasons to isolate transaction logs, or DB2 journals, into a separate ASP: 1 - To not have disk arms thrashing when the same arm tries to update a nsf, and a transaction log. 2 - Data protection. If drives fail in your primary ASP, you can restore the data to it, then apply the logs (or journals) from the secondary ASP to bring them up to date. Now I am not sure if transaction logging is as robust in this fashion as journalling as I've not played with transaction logging. Then again, we don't mess with the secondary ASP for what few journals we use either. Rob Berendt
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
