Date: Thu, 28 Mar 2024 10:37:10 +0000 (UTC) Message-ID: <85342400.67851.1711622230835@ip-10-0-1-26.ec2.internal> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_67850_1333902723.1711622230832" ------=_Part_67850_1333902723.1711622230832 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Scripting Options are listed on the second tab of the IDERA SQL = Data Compare Options window. Those options affect the way the synchronizati= on script is generated but do not affect the comparison operation.
Transaction size. Determines the max. size of the S=
QL Server transaction, under which the synchronization script runs. In some=
cases, the synchronization script can get extremely large, with millions o=
f insert/update/delete statements. Wrapping such a large script in a single=
transaction may not be possible, due to the transaction size limitations, =
or acceptable, for performance and other reasons. Setting a max. transactio=
n size is a way around these restrictions. If the transaction has a max. si=
ze, data compare commits the current transaction when the max. size is reac=
hed and starts a new one.
To have a transaction with no upper limit, set the max transaction size to=
0.
Please use this option with caution. If you set a max. transaction limit= and the synchronization process is canceled, only the current, open transa= ction is rolled back. Changes committed prior to that transaction are perma= nent and cannot be reversed. We strongly recommend, if possible, to leave t= he transaction unlimited, since it ensures that all changes in the database= are either committed or rolled back.
Save
Save