Hi guys,
Can I get your opinion on this? I am loading a lot of data using the DIRECT and NO COMMIT options of the COPY command. Then I run the ANALYZE_CONSTRAINTS() function on the table. If I find duplicates I rollback. Do you think it'd be faster if I did not use the AUTO option instead of DIRECT in this situation? I would think rolling back data changes on disk (ROS) would be slower than memory (WOS), or does it not matter?
What do y'all think?
COPY DIRECT vs AUTO with ROLLBACK
Moderator: NorbertKrupa
Re: COPY DIRECT vs AUTO with ROLLBACK
Hi!
Probably it will be faster (and I believe it will be faster, because as you pointed it will be in memory).
1. But on the other hand you will need to manage Tuple Mover (for intensive loads big chance to get "too much ROS containers")
2. It's memory overhead (data in memory). What about other users?
If you have enough memory and you succeed to configure TM so go on it!
Probably it will be faster (and I believe it will be faster, because as you pointed it will be in memory).
1. But on the other hand you will need to manage Tuple Mover (for intensive loads big chance to get "too much ROS containers")
2. It's memory overhead (data in memory). What about other users?
If you have enough memory and you succeed to configure TM so go on it!
Re: COPY DIRECT vs AUTO with ROLLBACK
Hi sKwa,
The load is happening at night when there aren't too many users online. I am just trying to get make sure I get the fastest rollback method so that I can fix what ever is wrong and reload the data as quickly as possible.
Thanks for your input!
The load is happening at night when there aren't too many users online. I am just trying to get make sure I get the fastest rollback method so that I can fix what ever is wrong and reload the data as quickly as possible.
Thanks for your input!