In Oracle's database, there is the concept of mirrored transaction logs. If
the primary copy of the transaction logs gets corrupt along with the
database, you can use the mirrored copy to recover the database (assuming the
mirrored copied didn't get corrupted as well). Does SQL Server provide for
similar capabilities?
Andrew D. Newbould - 10 Oct 2006 00:23 GMT
>In Oracle's database, there is the concept of mirrored transaction logs. If
>the primary copy of the transaction logs gets corrupt along with the
>database, you can use the mirrored copy to recover the database (assuming the
>mirrored copied didn't get corrupted as well). Does SQL Server provide for
>similar capabilities?
One common practice is to replicate the database onto another server and
use Transaction Log Shipping to keep them in sync. IMO it tends to
generate less traffic than replication. We use it for ALL customer
databases every 15 mins to a remote backup data centre. This way the
maximum data a Customer looses is the Last 15 Mins.

Signature
Andrew D. Newbould E-Mail: andrewn@zadsoft.com
ZAD Software Systems Web : www.zadsoft.com
Sue Hoegemeier - 10 Oct 2006 00:37 GMT
If your reason for using multiple members for the redo log
was to eliminate a single point of failure at the hardware
level, the correct Raid setup will mirror the log (or the
data files) at the hardware level. That's generally the
consideration in the SQL Server world.
-Sue
>In Oracle's database, there is the concept of mirrored transaction logs. If
>the primary copy of the transaction logs gets corrupt along with the
>database, you can use the mirrored copy to recover the database (assuming the
>mirrored copied didn't get corrupted as well). Does SQL Server provide for
>similar capabilities?
burt_king - 27 Nov 2006 19:59 GMT
No, SQL Server doesn't allow mirroring logs.....

Signature
burt_king@yahoo.com
> In Oracle's database, there is the concept of mirrored transaction logs. If
> the primary copy of the transaction logs gets corrupt along with the
> database, you can use the mirrored copy to recover the database (assuming the
> mirrored copied didn't get corrupted as well). Does SQL Server provide for
> similar capabilities?