How Do I Prevent a Sharp Increase in Data Disk Usage If I Want to Push a Large Amount of Data to My RDS for SQL Server Instance in a Short Period of Time?

If you push a large amount of data to your primary/standby instance in a short period of time, the data may not be able to be synchronized between the primary and standby instances fast enough. As a result, logs cannot be truncated or shrunk, and the disk usage spikes.

• Method 1

  Push data in batches, and leave plenty of time for each batch of data to be replicated from the primary instance to the standby instance.

• Method 2

  Before pushing data, set Recovery model of your database to Simple. In this model, data is not synchronized between the primary and standby instances, and no incremental backups are generated. During this period, point-in-time recovery (PITR) cannot be performed. After the data is pushed, set Recovery model of your database to Full to resume the replication between the primary and standby instance. For details, see How Do I Remove and Re-establish a Replication of My RDS for SQL Server Instance?

• Solution 3

  To migrate an on-premises database to your RDS instance, use DRS to restore backup files of the on-premises database to your RDS instance.