Correct.
SQL Server can have multiple transaction logs (I discovered this last week
while reading so I am correcting a previous post of mine here), but these
inevitably fill up. You then either do a backup log filename to device
truncate only to clear the log. This is the equivalent of running
Actually, MS transaction log(s) combine the functions of Oracle's redo logs
and Rollback segments (and that's bad).
As for archiving - nop, no archiving in MS SQL Server.
Igor Neyman, OCP DBA
Perceptron, Inc.
(734)414-4627
[EMAIL PROTECTED]
- Original Message -
To: Multiple recipients
