Specifies the number of rows sent in a bulk transfer before a commit is issued.
BulkCommitCount=integer
0–32767
0
integer is the number of rows sent in a bulk transfer.
If the value is 0, the DB2 access service issues a commit at the end of the transfer. If the value is non-zero, the DB2 access service issues a commit after every n rows. For example, if BulkCommitCount is set to 50, a commit is issued after every 50 rows.
The BulkCommitCount property is useful when you make large transfers to Adaptive Server and, as a result, run out of page locks on SQL Server. Issuing a commit after every n rows clears the page locks.
With this property, after rows are committed, they cannot be rolled back. Therefore, if you set BulkCommitCount to a non-zero value and a transfer fails, the DB2 access service rolls back only the batch containing data since the last commit was issued.
Setting BulkCommitCount can reduce bulk transfer performance when transferring data from the secondary database into DB2. This occurs because the DB2 access service sends as many rows as possible to DB2 in a single transfer but never more than the BulkCommitCount setting. If setting BulkCommitCount reduces transfer performance to DB2, try increasing the BulkCommitCount setting until performance is similar to that achieved with BulkCommitCount=0.
For more information on bulk transfer copy, see Chapter 9, “Using Bulk Copy Transfer.”.
| Copyright © 2005. Sybase Inc. All rights reserved. |
|
|
