Transaction logs full
From: Robert Stearns <rstearns1241_at_charter.net>
Date: Mon, 07 Jun 2004 21:59:16 -0400
Message-ID: <10ca7bkhqthk8d1_at_corp.supernews.com>
Is there a way (SQL syntax or some preparatory command) to cause a statement which implies a possibly large number of operation, either insert or update, to commit every so many rows? In particular the new 'merge ... when not matched insert ...' statement can consume large amounts of log space, depending on the number of 'not matched' rows. Received on Tue Jun 08 2004 - 03:59:16 CEST
Date: Mon, 07 Jun 2004 21:59:16 -0400
Message-ID: <10ca7bkhqthk8d1_at_corp.supernews.com>
Is there a way (SQL syntax or some preparatory command) to cause a statement which implies a possibly large number of operation, either insert or update, to commit every so many rows? In particular the new 'merge ... when not matched insert ...' statement can consume large amounts of log space, depending on the number of 'not matched' rows. Received on Tue Jun 08 2004 - 03:59:16 CEST