Data Replication 2
Results 1 to 2 of 2

Thread: On-Premise SQL Server to Amazon RedShift

  1. #1
    iamhasib is offline Junior Member
    Join Date
    Dec 2014
    Posts
    7
    Rep Power
    0

    On-Premise SQL Server to Amazon RedShift

    Appreciate your guidance and tips on the below -

    Started a 3.24 TB SQL Server (On-premise) which has about 105 files. All completed except 2, which are around 1.3 TB. Currently, going at a very slow speed. By the way, our SQL Server is connected to AWS via Direct Connect.

    I found this performance tip CloudBeam for Amazon Redshift -- Performance Tuning | Attunity. So can one of you please confirm the steps -

    1. Stop the current job
    2. Make the configuration change.
    3. Resume the job.

    Double checking as the process has been running for 20 hours and wouldn't want to lose what's been transferred already.

    Thank you all.

  2. #2
    stevenguyen is offline Senior Member
    Join Date
    May 2014
    Posts
    299
    Rep Power
    6
    Quote Originally Posted by iamhasib View Post
    Appreciate your guidance and tips on the below -

    Started a 3.24 TB SQL Server (On-premise) which has about 105 files. All completed except 2, which are around 1.3 TB. Currently, going at a very slow speed. By the way, our SQL Server is connected to AWS via Direct Connect.

    I found this performance tip CloudBeam for Amazon Redshift -- Performance Tuning | Attunity. So can one of you please confirm the steps -

    1. Stop the current job
    2. Make the configuration change.
    3. Resume the job.

    Double checking as the process has been running for 20 hours and wouldn't want to lose what's been transferred already.

    Thank you all.
    ====

    Since your SQL server is on Premise and your Replicate server is on AWS, you are not taking advantage of our Data transfer through the Attuntiy Cloudbeam server to S3.

    It recommended to have the Replicate server closest to your Source, in your case, the Attunity Replicate server need to be on Premise closest to your SQL server.

    Therefore, when Attunity Replicate could read the data on your SQL source much faster and transfer the data to S3 much faster using our Transfer engine and utilizing the Attunity Cloudbeam Server.

    ----

    The Performance turning that you refer to would not help since your Replicate server is on AWS.

    Also, you would need to stop and reload your table if the target Database Definition got update.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •