Re: Moving data from MS SQL to Google cloud SQL

[Takashi Matsuo]

Hi Patrick,

Since Cloud SQL only offers Web based interface, I would suggest using
existing tools for migration to local MySQL environment first, then
taking mysql dump, uploading the dump to Google Cloud Storage, and
then importing your dump to the Cloud SQL instance.

For more details, please see:
https://developers.google.com/cloud-sql/docs/import_export

You can also create your own migration tool by using google_sql.jar:
https://developers.google.com/cloud-sql/docs/external

Hope it helps,

-- Takashi

On Thu, Jun 21, 2012 at 7:06 AM, Pat <patrick....@bairdwarner.com> wrote:
> What are the best ways to move a few tables from an MS SQL database to the
> google cloud SQL for use with app engine? The tables are mostly not that big
> (a few thousand records), and some will need to be updated somewhat often.



--
Takashi Matsuo | Developer Advocate | tma...@google.com

[Ken Ashcraft]

On Thu, Jun 21, 2012 at 11:57 AM, Pat <patrick....@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

[Rori Stumpf]

I recently migrated a small-ish database from SQL Server 2008 to MySQL. It wasn't as simple as I had expected, but wasn't that difficult either. Take a look at this thread for ideas:  http://stackoverflow.com/questions/129/how-to-export-data-from-sql-server-2005-to-mysql 

I ended up using SSIS.