Rows Per Commit - Utility Mode-MSSQL DB

Download as doc, pdf, or txt
Download as doc, pdf, or txt
You are on page 1of 1

Rows Per Commit - Utility Mode- MSSQL DB

ITtoolbox as adapted from Abinitio-L discussion group Summary: What exactly does rows per commit parameter in an output table specify when the mssql_interface is utility? Full Article: Disclaimer: Contents are not reviewed for correctness and are not endorsed or recommended by ITtoolbox or any vendor. Popular Q&A contents include summarized information from ITtoolbox Abinitio-L discussion unless otherwise noted.
1/3/2006 By ITtoolbox Popular Q&A Team for

Adapted from a response by Remediator on 12/30/2005 The commit count simply keeps short accounts on the internal commit log. If you use it and the load fails, SQLServer will only rollback to the most recent count. So if your load has 40 records with a commit count of 10, and fails on the 37th record, 30 of the records will commit and 7 will rollback. Some people like to use this mode because it offers better performance on loads with millions of rows. Your actual performance may vary. If you don't use a commit table, the commit log will typically keep every single loaded row in the rollback segment so it can back them all out in case of failure - this can get expensive for millions of records.

You might also like