Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from http://cloud.google.com/sql/docs/postgres/upgrade-cloud-sql-instance-to-enterprise-plus-vpc-peering below:

Upgrade an instance to Cloud SQL Enterprise Plus edition by using VPC peering | Cloud SQL for PostgreSQL

Stay organized with collections Save and categorize content based on your preferences.

This page shows you how to use the private VPC peering network connectivity method of Database Migration Service to upgrade a Cloud SQL Enterprise edition instance to Cloud SQL Enterprise Plus edition. Database Migration Service creates a new Cloud SQL instance and migrates data to that instance.

Cloud SQL Enterprise Plus edition is ideal for applications that require maximum write performance. For more information about these improvements, see Performance enhancements.

To enable these enhancements for your existing Cloud SQL Enterprise edition instances, you must upgrade them to Cloud SQL Enterprise Plus edition using Database Migration Service.

1. Sign in to your Google Cloud account. If you're new to Google Cloud, create an account to evaluate how our products perform in real-world scenarios. New customers also get $300 in free credits to run, test, and deploy workloads.

2. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

3. Make sure that billing is enabled for your Google Cloud project.

4. In the Google Cloud console, on the project selector page, select or create a Google Cloud project.

   Note: If you don't plan to keep the resources that you create in this procedure, create a project instead of selecting an existing project. After you finish these steps, you can delete the project, removing all resources associated with the project.

   Go to project selector

5. Make sure that billing is enabled for your Google Cloud project.

6. Enable the Database Migration Service API.

   Enable the API

7. Make sure that you have the Database Migration Admin role assigned to your user account.

   Go to IAM

Database Migration Service offers various source database options and network connectivity methods. Different sources work better with some connectivity methods than with others. On this page, we assume that you're using a Cloud SQL Enterprise edition instance in an environment where you can configure your network to add an inbound firewall rule. Because we can't know the specifics of your environment, we can't provide detailed steps when it comes to your networking configuration.

To configure your source Cloud SQL Enterprise edition instance, complete the following steps:

1. If you don't have the postgres database for your source instance, then create one. For more information, see Create a database on the Cloud SQL instance.
2. Install the pglogical package on the databases of your source instance. Make sure that the package is included in the shared_preload_libraries variable. For more information, see Configure your source databases.
3. Enable logical replication and decoding for the databases of your source instance. For more information, see Enable logical replication and decoding for your source databases.

Note: For PostgreSQL 9.4, install the pglogical_origin extension. Then, install the extension on every database by running the following commands:

• CREATE EXTENSION IF NOT EXISTS pglogical_origin;
• CREATE EXTENSION IF NOT EXISTS pglogical;

Aside from the template0 and template1 databases, Database Migration Service migrates every other database under your source Cloud SQL Enterprise edition instance.

On each database in your source instance that isn't mentioned above, complete the following steps:

1. To install the pglogical extension into the database, run the CREATE EXTENSION IF NOT EXISTS pglogical command.

2. For any tables that don't have primary keys, migrate the UPDATE and DELETE statements manually.

   Note: For tables that don't have primary keys, Database Migration Service supports migration of the initial snapshot and INSERT statements during the change data capture (CDC) phase.

   To learn how to generate a query to list tables in a PostgreSQL database without primary keys, see Debugging and other tools. For each database table that you find that doesn't have a primary key and the table isn't part of the databases that aren't migrated, alter the table so that it has a primary key or migrate the UPDATE and DELETE operations for the table. For tables that don't have primary keys, only the initial snapshot and INSERT statements are migrated.

3. To set these privileges on each of the migrated databases, create a user or set the privileges of an existing user. You use this user to connect to the source instance, and you configure this user as the user in the Connection profiles page. This user must have certain privileges on each of the migrated databases, as well as the default postgres database.

   To set these privileges, connect to the instance and run the following commands:

   1. GRANT USAGE on SCHEMA SCHEMA to USER on all schemas (aside from the information schema and schemas starting with pg_) on each database that you want to migrate.
   2. GRANT USAGE on SCHEMA pglogical to PUBLIC; on each database that you want to migrate.
   3. GRANT SELECT on ALL TABLES in SCHEMA pglogical to USER on all databases to get replication information from source databases.
   4. GRANT SELECT on ALL TABLES in SCHEMA SCHEMA to USER on all schemas (aside from the information schema and schemas starting with pg_) on each database that you want to migrate.
   5. GRANT SELECT on ALL SEQUENCES in SCHEMA SCHEMA to USER on all schemas (aside from the information schema and schemas starting with pg_) on each database that you want to migrate.
   6. ALTER USER USER with REPLICATION role

Enable logical replication and decoding for the databases of your source Cloud SQL Enterprise edition instance by setting the cloudsql.logical_decoding and cloudsql.enable_pglogical flags to On. For more information about these flags, see Configure database flags.

To enable both of these flags, complete the following steps:

1. In the Google Cloud console, go to the Cloud SQL Instances page.

   Go to Cloud SQL Instances

2. Click your source instance.
3. Click Edit.
4. In the Customize your instance section, if the Show configuration options menu appears, then click it.

5. Expand the Flags section.

6. To set the cloudsql.logical_decoding and cloudsql.enable_pglogical flags, complete the following steps:

   1. Click Add a database flag.
   2. From the drop-down menu, choose the cloudsql.logical_decoding flag.
   3. Set the value for this flag to On.
   4. Click Done.
   5. Repeat these steps for the cloudsql.enable_pglogical flag.

7. Click Save.

8. In the Changes require restart dialog, click Save and restart. Cloud SQL restarts your source instance so that the configuration changes that you made to the flags can take effect.

9. In the Configuration pane, confirm your changes in the Database flags section.

To upgrade a source Cloud SQL Enterprise edition instance, you must retrieve the following information:

• The instance's private IP address. You use this IP address when you create a connection profile in Database Migration Service.
• The name of the VPC network that allows the Cloud SQL Enterprise Plus edition destination instance to communicate with the Cloud SQL Enterprise edition source instance directly. You use this VPC network when you create a migration job in Database Migration Service.

To retrieve information from the source Cloud SQL Enterprise edition instance, complete the following steps:

1. In the Google Cloud console, go to the SQL Instances page.

   Go to Cloud SQL Instances

2. Click your source instance.
3. In the Connect to this instance section, click Copy to clipboard in the Private IP address field.
4. At the top of the page, click Edit.
5. Expand the Connections section.
6. In the Associated networking section, make a note of the name of the VPC network that appears in the Network field.

A connection profile contains information about the source Cloud SQL Enterprise edition database. Database Migration Service uses the information in the connection profile to migrate data from your source database to the destination Cloud SQL Enterprise Plus edition instance.

To create a connection profile, complete the following steps:

1. In the Google Cloud console, go to the Connection profiles page in Database Migration Service.

   Go to Connection profiles

2. Click Create profile.

3. From the Database engine drop-down list, select Cloud SQL for PostgreSQL.

4. In the Connection profile name field, enter a name for the connection profile for your source database, such as My Connection Profile.

   Note: Cloud SQL generates the connection profile ID automatically with information about your source instance. We recommend that you don't change this value.

5. Select the region where you want to save the connection profile.

   Note: Connection profiles, like all resources, are saved in a region. Region selection doesn't affect which migration jobs can use connection profiles, or which regions can connect to the data location. But region selection can affect availability in the case of regional downtime.

6. From the Cloud SQL instance drop-down list, select the name of your Cloud SQL Enterprise edition instance.

7. In the Hostname or IP address field, replace the value with the private IP address that you copied in Retrieve information from the source Cloud SQL Enterprise edition instance.

8. To authenticate to your source instance, enter a username and password. Then, click Continue.

   Note: Cloud SQL populates the Port field automatically with information about your source instance. If this field is empty, then enter the appropriate port number.

9. If you want to encrypt your data, then enable SSL/TLS encryption for the connection between the source and destination databases. Otherwise keep the default value of None.

10. Click Continue.

11. From the Connectivity test drop-down menu, select Not defined.

12. Click Create.

Database Migration Service uses migration jobs to migrate data from your source Cloud SQL Enterprise edition database instance to the destination Cloud SQL Enterprise Plus edition instance.

Creating a migration job includes the following steps:

• Defining settings for the job.
• Selecting the connection profile that you created for your source Cloud SQL Enterprise edition database. This is your source connection profile.
• Defining settings for the destination Cloud SQL Enterprise Plus edition instance.
• Setting up connectivity between the source and destination database instances.
• Testing the migration job to ensure that the connection information that you provided for the job is valid.

1. In the Google Cloud console, go to the Migration jobs page in Database Migration Service.

   Go to Migration jobs

2. Click Create migration job.

3. In the Migration job name field, enter a name for the migration job, such as My Migration Job.

4. From the Source database engine drop-down list, select Cloud SQL for PostgreSQL.

5. From the Destination database engine drop-down list, select Cloud SQL for PostgreSQL.

6. Select the destination region where the Cloud SQL Enterprise Plus edition instance is created.

7. From the Migration job type drop-down list, select Continuous because you want ongoing changes in your source Cloud SQL Enterprise edition database to be migrated to the destination Cloud SQL Enterprise Plus edition instance.

8. Review the required prerequisites that are generated automatically to reflect how the environment must be prepared for a migration job. These prerequisites can include how to configure the source Cloud SQL Enterprise edition database and how to connect it to the destination Cloud SQL Enterprise Plus edition instance.

   It's recommended to complete these prerequisites at this step, but you can complete them at any time before you test or start your migration job.

9. Click Save & continue.

1. From the Select source connection profile drop-down list, select the connection profile that you created.

2. Click Save & continue.

1. In the Password field, enter an alphanumeric password for the destination Cloud SQL Enterprise Plus edition instance. This is the password for the postgres administrator account in the instance.

2. From the Database version drop-down list, select the destination instance from the list of supported Cloud SQL versions for the specified database engine.

3. Select Enterprise Plus.

4. From the Choose region and zone section, select the desired Google Cloud zone for the new Cloud SQL Enterprise Plus edition instance (or leave as Any).

5. Select the Private IP checkbox.

6. From the VPC drop-down list, select the VPC network that you noted in Retrieve information from the source Cloud SQL Enterprise edition instance.

7. Select the machine shape for the Cloud SQL Enterprise Plus edition instance. The disk size must be equal to or greater than the source database size.

8. Define the storage type and storage capacity for the Cloud SQL instance.

9. To create the new instance, click Create & Continue.

10. In the dialog that appears, click Create destination & continue. Creating the instance may take several minutes to complete.

    Important: This procedure creates a Cloud SQL Enterprise Plus edition instance. You're charged according to the configuration that you select.

1. Choose how you'd like to use to establish connectivity between the source Cloud SQL Enterprise edition and destination Cloud SQL Enterprise Plus edition databases. For this procedure, use the Connectivity method drop-down list to select Source and destination are using private IP.
2. From the VPC drop-down list, select the VPC network where your source Cloud SQL Enterprise edition instance resides. This is the VPC network that you noted in Retrieve information from the source Cloud SQL Enterprise edition instance.
3. Click Configure & continue.

1. Review the settings that you chose for the migration job.

2. Verify that the source has been configured correctly, that the source Cloud SQL Enterprise edition and destination Cloud SQL Enterprise Plus edition instances are able to communicate with each other, and that the migration job is valid:

   1. Click Test job.

   2. Verify that you see the Your migration job test was successful! status.

   If the test fails, then you can address the problem in the appropriate part of the flow, and return to re-test.

3. To create the migration job and start it immediately, click Create & start job.

4. In the dialog that appears, click Create & start.

5. In the Migration jobs page, verify that your migration job has a status of Starting.

6. After a few minutes, confirm that the status changes to Running.

To confirm that Database Migration Service used the migration job to migrate data from your source Cloud SQL Enterprise edition database instance to the destination Cloud SQL Enterprise Plus edition database instance, complete the following steps:

1. In the Google Cloud console, go to the SQL Instances page.

   Go to Cloud SQL Instances

2. Click the read replica entry of your migration job.

   Note: Make sure that the Cloud SQL edition for this entry is Enterprise Plus, and not Enterprise.
3. Click the Activate Cloud Shell icon that appears next to the Search field.

4. At the prompt, to connect to the destination Cloud SQL Enterprise Plus edition database instance, use the gcloud sql connect command.

   gcloud sql connect DESTINATION_INSTANCE_NAME --user=postgres

   Replace DESTINATION_INSTANCE_NAME with the name of the destination Cloud SQL Enterprise Plus edition instance.

5. Optional: If an Authorize Cloud Shell dialog appears, then click Authorize.
6. At the Enter password prompt, enter the password that you provided in Define settings for the destination Cloud SQL Enterprise Plus edition instance.

1. At the postgres prompt, to list the databases and verify that you see your source Cloud SQL Enterprise edition database instance, enter \list.
2. At the postgres prompt, to see the tables that are associated with this database instance, enter \connect SOURCE_DB_NAME. The name of the prompt changes from postgres to SOURCE_DB_NAME.
3. At the SOURCE_DB_NAME prompt, to see the tables of this instance, enter \dt.
4. At the SOURCE_DB_NAME prompt, to give this user permission to access the data in the tables of this instance, enter GRANT cloudsqlexternalsync to USER;.

   Replace USER with the name of the user that you used to connect to the destination Cloud SQL Enterprise Plus edition database instance.

5. At the SOURCE_DB_NAME prompt, to see the information that's replicated from a table in your source Cloud SQL Enterprise edition database instance, enter SELECT * from TABLE_NAME;.
6. Verify that you see the correct information in the table.

Promoting the migration job replaces the source Cloud SQL Enterprise edition database instance with the destination Cloud SQL Enterprise Plus edition database instance as the primary database.

To promote the migration job, complete the following steps:

1. Return to the Migration jobs page.

2. Click the migration job that you want to promote. The Migration job details page appears.

3. Stop all writes to the source Cloud SQL Enterprise edition database.

   Important: Before you stop writes to the source database, wait for the replication delay to be minimal. You must stop all writes to this database because, by promoting the migration job, the destination Cloud SQL Enterprise Plus edition database becomes your primary database.

4. Verify that the replication delay is minimal.

5. Click the migration job that you want to promote. This job has a status of Running.

6. To promote the migration job, click Promote.

7. In the dialog that appears, click Promote.

8. Verify that the migration job has a status of Promote in progress. After a few minutes, confirm that the status changes to Completed.

Your new Cloud SQL Enterprise Plus edition database instance is ready to use.

To avoid incurring charges to your Google Cloud account for the resources used on this page, use the Google Cloud console to delete your migration job, connection profile, source Cloud SQL Enterprise edition instance, and project if you don't need them.

• Read more about the key features of Cloud SQL Enterprise Plus edition.
• Read more about performance enhancements for Cloud SQL Enterprise Plus edition.
• Read more about region support for Cloud SQL Enterprise Plus edition.
• Read more about pricing for Cloud SQL Enterprise Plus edition.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-14 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-14 UTC."],[],[]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4