The 'Exporting data from Cloud SQL 
<https://cloud.google.com/sql/docs/import-export#export>' and 'Importing 
data to Cloud SQL <https://cloud.google.com/sql/docs/import-export#import>' 
articles provide very succinct guides on how to achieve the exporting and 
importing you seek. As there is no single click feature for you to modify a 
1st generation Cloud SQL to a 2nd generation, you will need to do the 
following:

   1. Create a 2nd generation instance to your liking and needs
   2. Export the data from the 1st generation instance (possibly to Cloud 
   Storage as in the article)
   3. Import the exported data into the new 2nd generation instance
   
This can be done very simply using the Developers Console 'Export' and 
'Import' features when a Cloud SQL instance is selected. As for the 
app.yaml, it should not be affected. You only needs to change the 
connection string being using and ensure you App Engine application is 
granted access to the new Cloud SQL instance.

Please note that the second generation Cloud SQL instance is still in Beta 
and as such, not covered by any Service Level Agreement.

Cheers,

On Wednesday, January 13, 2016 at 4:52:43 AM UTC-5, Jukka Hautakorpi wrote:
>
> I have php +cloud sql app and i would like to move the database / instance 
> to the new beta.
> How can i export and import the data ? 
> How can i configure the my app.yaml or so to use the new beta instance ?
>
> I can do it so that there is accepted downtime, during the weekend.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/311d0ada-60a7-44bc-91b4-a54503842938%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to