Stay organized with collections
Save and categorize content based on your preferences.
This page shows you how to create a conversion workspace and use
it to immediately perform deterministic code and schema conversion from
SQL Server to PostgreSQL. Before you create the workspace,
make sure that you
create a connection profile for your source database.
When you create a conversion workspace, you can upgrade it to access
Gemini auto-conversion.
Upgrading the workspace is possible only once,
immediately after you open the newly created conversion workspace.
This operation is described as the last step in this procedure.
To create a conversion workspace and perform the schema
conversion, do the following:
In the Google Cloud console, go to Conversion workspaces.
On the Create a conversion workspace page, do the following:
Enter the name, identifier, and region for your conversion workspace.
From the Source database engine drop-down menu, select your source
SQL Server database.
From the Destination database engine select
AlloyDB for PostgreSQL.
Click Create workspace and continue.
On the Define source and pull schema snapshot page, do the following:
From the Source connection profile drop-down menu, select the connection
profile for your source database.
Click Pull schema snapshot and continue.
Database Migration Service is now connecting to the source database and retrieving your schema.
This process can take several minutes.
On the Select and convert objects page, use the checkboxes to select which objects
you want to convert to PostgreSQL syntax.
You don't have to convert all your objects in one go. Instead, you can
select just a few objects now and
add more objects to the conversion later.
Click Convert and continue.
The conversion workspace opens.
When you open a new workspace for the first time, you can upgrade it to
access the Gemini-powered auto-conversion feature.
Do the following:
In the Introducing Gemini auto-conversion dialog, select the
Upgrade workspace to explore the new experience checkbox, and click
Continue.
In the Convert source objects with Gemini? dialog,
click Convert.
Database Migration Service now performs the conversion process again to
apply Gemini-powered conversion enhancements
on top of the deterministic conversion results.
For more information on Gemini auto-conversion
feature, see
Gemini auto-conversion.
What's next
You can now work with your conversion workspace to fix conversion issues,
modify your objects with the interactive editor, and apply converted schema
to your destination database. See
Convert SQL Server code and schema to PostgreSQL syntax.
[[["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-09-09 UTC."],[[["\u003cp\u003eThis feature provides a Database Migration Service for migrating heterogeneous SQL Server databases to AlloyDB for PostgreSQL.\u003c/p\u003e\n"],["\u003cp\u003eThe service is currently in a pre-GA phase, meaning it is available "as is" with potentially limited support as per the General Service Terms.\u003c/p\u003e\n"],["\u003cp\u003eUsers can create a conversion workspace to perform automated code and schema conversion, starting by setting up a connection profile for their SQL Server database.\u003c/p\u003e\n"],["\u003cp\u003eThe migration process involves defining source and destination databases, pulling a schema snapshot, and selecting objects for conversion, with the option to add more objects later.\u003c/p\u003e\n"],["\u003cp\u003eOnce converted, users can fix issues, modify objects in an editor, and apply the converted schema to their AlloyDB for PostgreSQL destination.\u003c/p\u003e\n"]]],[],null,["# Create a conversion workspace and convert schema\n\nThis page shows you how to create a conversion workspace and use\nit to immediately perform deterministic code and schema conversion from\nSQL Server to PostgreSQL. Before you create the workspace,\nmake sure that you\n[create a connection profile for your source database](/database-migration/docs/sqlserver-to-alloydb/create-source-connection-profile).\n\nWhen you create a conversion workspace, you can upgrade it to access\n[Gemini auto-conversion](/database-migration/docs/sqlserver-to-alloydb/code-conversion-with-gemini#auto-conversion).\nUpgrading the workspace is possible only once,\nimmediately after you open the newly created conversion workspace.\nThis operation is described as the last step in this procedure.\nTo create a conversion workspace and perform the schema\nconversion, do the following:\n\n1. In the Google Cloud console, go to **Conversion workspaces** .\n\n [Go to Conversion workspaces](https://console.cloud.google.com/dbmigration/conversion-workspaces)\n2. Click **Set up workspace**.\n3. On the **Create a conversion workspace** page, do the following:\n 1. Enter the name, identifier, and region for your conversion workspace.\n 2. From the **Source database engine** drop-down menu, select your source SQL Server database.\n 3. From the **Destination database engine** select **AlloyDB for PostgreSQL**.\n 4. Click **Create workspace and continue**.\n4. On the **Define source and pull schema snapshot** page, do the following:\n 1. From the **Source connection profile** drop-down menu, select the connection profile for your source database.\n 2. Click **Pull schema snapshot and continue**.\n\n Database Migration Service is now connecting to the source database and retrieving your schema.\n This process can take several minutes.\n5. On the **Select and convert objects** page, use the checkboxes to select which objects you want to convert to PostgreSQL syntax.\n\n You don't have to convert all your objects in one go. Instead, you can\n select just a few objects now and\n [add more objects to the conversion](/database-migration/docs/sqlserver-to-alloydb/work-with-conversion-workspaces#add-source-objects) later.\n6. Click **Convert and continue** .\n\n The conversion workspace opens.\n7. When you open a new workspace for the first time, you can upgrade it to access the Gemini-powered auto-conversion feature. Do the following:\n - In the **Introducing Gemini auto-conversion** dialog, select the **Upgrade workspace to explore the new experience** checkbox, and click **Continue**.\n - In the **Convert source objects with Gemini?** dialog, click **Convert** .\n\n Database Migration Service now performs the conversion process again to\n apply Gemini-powered conversion enhancements\n on top of the deterministic conversion results.\n For more information on Gemini auto-conversion\n feature, see\n [Gemini auto-conversion](/database-migration/docs/sqlserver-to-alloydb/code-conversion-with-gemini#auto-conversion).\n\nWhat's next\n-----------\n\nYou can now work with your conversion workspace to fix conversion issues,\nmodify your objects with the interactive editor, and apply converted schema\nto your destination database. See\n[Convert SQL Server code and schema to PostgreSQL syntax](/database-migration/docs/sqlserver-to-alloydb/convert-sql)."]]
