|Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM ODBC Driver » View Thread|
|Messages 1 to 3 of 3 total|
|DBISAM START TRANSACTION|
|Wed, Jun 24 2015 3:49 PM||Permanent Link|
When inserting rows into a table using a transaction, are there any recommended limits on how many rows one can attempt to insert before COMMIT FLUSH should be used?
|Wed, Jun 24 2015 4:58 PM||Permanent Link|
On 6/24/2015 3:49 PM, James Summerlin wrote:
> When inserting rows into a table using a transaction, are there any recommended limits on how many rows one can attempt to insert before COMMIT FLUSH should be used?
The general guidelines are to keep them short so you don't write lock
the database/table for extended periods of time. For multi-user acces
this is relevant but if your app is the only one accessing the data then
it's often of lesser importance.
The other limitations is that during the transaction all data is cached
in memory so you do need to look out for RAM usage (especially since
commit will result in additional RAM requirements as data is getting
written to table in addition to cache size).
Final issue is that the actual commit might take a while as well with
lots of records so you have increased risk of data corruption should you
lose power in the middle of it (or somebody terminates the app thru task
|Wed, Jun 24 2015 10:21 PM||Permanent Link|
Thank you, Raul.