I am away from my desk so can't do any experimenst, but I just wondered whether moving from StartTransaction/Append/Post/Commit to using a TUniLoader is likely to make any difference to the speed at which I load data into a database.
I have a few million records to insert and time is of the essense. Is either one of these likely to be faster than the other, or are they basically the same operation?
transactions or TUniLoader - which is faster
Re: transactions or TUniLoader - which is faster
Hello,
In most cases, UniLoader will work faster than using transactions, since special DB mechanisms are used for data loading. In some providers, UniLoader has an already embedded mechanism of automatic work with transactions during loading.
In most cases, UniLoader will work faster than using transactions, since special DB mechanisms are used for data loading. In some providers, UniLoader has an already embedded mechanism of automatic work with transactions during loading.
Re: transactions or TUniLoader - which is faster
Thanks alex - moving to uniloader
Re: transactions or TUniLoader - which is faster
Hello,
If you have any other questions, feel free to contact us.
If you have any other questions, feel free to contact us.