Great article, I should have come here first.
This thread may be a little old and there may be new features added to the Amazon RDS. But here is my situation.
I have a VLD I need to move to the Amazon RDS. But lets start at the beginning.
I have an instance of the Amazon RDS set up. I scripted out the production VLD structure and was able to successfully put it into place on the Amazon RDS. So far so good.
Now for data. I have several tables that are over 10m rows each. One is about 80m rows. If I use the Red-Gate SQL Data compare it builds the deployment script local to the C: drive causing SQL Data Compare to stop working along with giving issues to the local host I'm working on.
I wrote my own syncing process, which does work however is not the most efficient. It works great on the smaller tables, pushing out the data changes by table out to the Amazon RDS. I have a process on the Amazon RDS side to load that data in. This process works without issue.
Now my VLT. I've considered using BCP to export/import the VLT data, using native format. I have a process that has automated this and it does work well. Just not sure how much time is needed to move all of the rows of data from these table to Amazon.
In an ideal world I'd like to be able to push a button and have a complete replica of my production database on the Amazon RDS.
What are my options? Maybe there is a way I can reconfigure the Red-Gate tool to store the deployment scripts to some other place than the C: drive of the host?
Any input on this would be greatly appreciated.
Kurt W. Zimmerman
New York, NY