Best practices for large tables

[jzambranodba]

Hi All,

I wanted to check what is the best practice for making changes to large replicated tables from SQL Server to Redshift using Attunity. We are currently on version 5.5.0.367 and we occasionally have to make changes to the table on the SQL Server instance like adding columns and changing data types.

Most of the time it works well but occasionally we have to reload the entire table because it was not able to apply the changes to redshift for whatever reason.

Due to the size of the tables it tends to cause latency to balloon and it affects other replicated tables under the same task.

I tried looking at the documentation and wasn't able to find any best practice recommendations for making changes to large replicated tables (or replicated tables in general).

Any advice or pointing me in the right direction would be appreciated.

[David_Fergen]

Hi Jazambranodba,

Thanks for the question! I noticed you are on version 5.5. I would highly recommend that you upgrade to 7.0 to take advantage of some of the new features that would help you vastly with your large tables. Some of these new features are parallel loading.

If you need any help in upgrading feel free to let us know! 

Thanks,

David

[lyka · Accepted solution]

Hello,

In Full Load replication mode, you can accelerate the replication of large tables by splitting the table into
segments and loading the segments in parallel. Tables can be segmented by data ranges, by partitions, or by
sub-partitions.

Please refer to the Replicate user guide for source and target endpoints that are supported when using Parallel load.

thanks,

Lyka