Plan for SQL Server 2017 End of Support: Starting April 12, 2027, you won't be able to create new Cloud SQL for SQL Server 2017 instances. You can use Database Migration Service to migrate and upgrade self-managed, Amazon RDS, or existing Cloud SQL for SQL Server 2017 instances to Cloud SQL for SQL Server 2019, 2022, or 2025. For timeline details, see Database versions and version policies.
Verify a migration
Stay organized with collections
Save and categorize content based on your preferences.
This page describes how to confirm that your migrated data is complete and
accurate. At a minimum, you should verify that your tables exist in the
migrated Cloud SQL for SQL Server databases instance.
Connect to your Cloud SQL for SQL Server instance with a tool where you can
run SQL commands against your migrated databases.
For more information on connecting to Cloud SQL instances, see
Connection options
in Cloud SQL documentation.
Run SQL commands to verify your migrated data. For example:
List all databases
Run the following command to verify if your destination Cloud SQL for SQL Server
contains all the source databases you wanted to migrate:
EXECsp_databases;GO
List all tables in a database
Run the following commands to check if your migrated database
contains all the necessary tables:
Start using a specific database:
USEDATABASE_NAME;GO
List all tables in the database:
SELECT*FROMinformation_schema.tables;
Check table content and definitions
Run the following commands to verify the correctness of a specific
migrated table:
[[["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 2026-11-10 UTC."],[],[]]