On Thu, Jun 21, 2012 at 11:57 AM, Pat <patrick.mcdonald@bairdwarner.com> wrote:
Thanks for the help. I tried it out and everything seems to work. But your suggestion also led me to another idea: What about just using a migration tool that reads the MS SQL database and outputs MySql scripts to recreate the database. But then instead of loading it into a local MySQL DB and running mysqldump, instead I'm just using the SQL command line tool to upload and run the sql file from the migration. Is this approach better or is there a possibly drawback that I'm missing?
The command line tool will run the sql statements serially. Because of the physical distance between your desktop and the Cloud SQL server, even the simplest of statements will likely have high latency. As a result, it will take much longer to upload your data. So unless you have a very small amount of data (e.g. 10MB), going through Cloud Storage is going to be many times faster.
Ken
No comments:
Post a Comment