Transaction logs full

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 Mon Jun 07 2004 - 20:59:16 CDT