And thus you discover the inane mechanism that SQL Server
inherited from Sybase, by which both try to do concurrency.
Guess what happens when a long running transaction marks
the log near the end, and not too long afterward the log
needs truncated?
If memory serves, ( hasn't worked too well lately :) the database
will hang. It may just truncate back to the mark, and start from
there, but you always have the possibility of another long
transaction starting.
Can't remember the details, but what I do remember clearly
is that it is a process that has to be closely watched, and I
didn't particularly care for the way it worked.
Jared
On Wednesday 30 May 2001 11:41, Gary Weber wrote:
> Halo,
>
> Windoz 2000/SQL Server 2000
>
> Bringing an axuliary MS SQL db online. Trying to setup "archiving". Am I
> reading documentation right, SQL does NOT automatically archive transaction
> log? This process must be setup via backup routine, which truncates the log
> upon completion?
>
> Lemme try some logic:
>
> Oracle's redo logs = MS transaction log(s)
> Oracle's archived logs = ?
>
>
> Gary Weber
> Senior DBA
> Charles Jones, LLC
> 609-530-1144, ext 5529
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Jared Still
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from). You may
also send the HELP command for other information (like subscribing).
