Convert SQL Server to PostgreSQL.

Our DBConvert/DBSync for MSSQL and PostgreSQL cross database migration software helps you to convert and synchronize your databases from Microsoft SQL Server to PostgreSQL / Amazon RDS PostgreSQL / Heroku Postgres and in any other possible combination of source and target . Also, Windows Azure SQL Databases may be set up as a source or target. Our program is able to connect to any local or remote MS SQL Server and PostgreSQL instances.

Although both MS SQL Server and PostgreSQL databases are ANSI-SQL compliant, there are still differences between their SQL syntax, data types, case sensitivity, and these differences often makes transferring data not so trivial if you try to do that manually.

The entire database can be copied from a MS SQL Server instance to a PostgreSQL instance or you can specify partial datasets in a customization stage for each migration.

Using Dump files and PHP load scripts as a destination would be alternative if there is no direct access to servers.


Once data is migrated, all updates can be synchronized from the MSSQL database to the PostgreSQL database can be performed smoothly with our DBSync for MSSQL and PostgreSQL.

Your database will always be up-to-date due to three sync types (Drop, Insert, Update).

Run the program at user-specified time intervals specifying settings at the scheduling stage. Scheduler runs automatically and unattended in the background.

 DBConvert for MSSQL & PostgreSQL

Migration directions:

  • MS SQL Server → PostgreSQL, MS SQL Dump, PostgreSQL Dump, PHP Script
  • PostgreSQL → MS SQL Server, MS SQL Dump, PostgreSQL Dump, PHP Script
  • PostgreSQL ↔ SQL Azure
  • MS SQL Server ↔ Amazon RDS ↔ PostgreSQL
  • MS SQL Server ↔ Heroku Postgres ↔ PostgreSQL

Version: 3.6.2

Release Date: June 15, 2018

 DBSync for MSSQL & PostgreSQL

Sync directions:

  • MS SQL Server ↔ PostgreSQL
  • PostgreSQL ↔ SQL Azure
  • MS SQL Server ↔ Amazon RDS ↔ PostgreSQL
  • MS SQL Server ↔ Heroku Postgres ↔ PostgreSQL

Version: 2.9.4

Release Date: Oct. 24, 2019

Try All-in-one DB migration and Sync software.

DBConvert Studio

 Version: 1.8.4

Release Date: Nov. 23, 2020

Supported databases:

  • SQL Server
  • MySQL
  • Oracle
  • PostgreSQL
  • Access
  • FoxPro
  • SQLite
  • Firebird
  • Excel
  • IBM DB2
  • Azure SQL
  • Amazon RDS
  • Amazon Aurora
  • Heroku Postgres
  • Google Cloud

Related Links

Supported OS:

Using SQL Server to PostgreSQL conversion and synchronization tools.

When you start DBConvert or DBSync application in GUI mode it guides you through several steps to set up the database migration or synchronization:

1. Connect to SQL Server source database.

If a source database requires you to log in, you can specify a user name/ password and host/ port parameters.

Connect to SQL Server source database from DBConvert

2. Connect to PostgreSQL destination database.

Specifying parameters for destination database looks like the same as for source. Usually, it consists of defining connection settings and username/password pairs.

Connect to PostgreSQL target database from DBConvert

NOTE #1: Every DBConvert or DBSync tool has two different databases in its name. That means any specified database from a pair can be set up as a source or destination. Besides, the same type of database may be set up both as a source or destination.

As an example, here is the list of possible migration directions with on-premises databases:

  • SQL Server to PostgreSQL
  • PostgreSQL to SQL Server
  • SQL Server to SQL Server
  • PostgreSQL to PostgreSQL

NOTE #2: Don't be confused by the fact that connections to cloud databases like Amazon RDS, Microsoft Azure SQL, Google Cloud, and Heroku are not explicitly specified in the configuration of a source or destination in the DBConvert / DBSync interface. To connect to Cloud database instances, use the same settings as you do for traditional on-premises databases.

NOTE #3: Your connections to source and target databases stay active until you close DBConvert/ DBSync application or reopen new connections on "source" and "destination" steps.

Read more about the specific source/ destination configurations for different databases.

3. Custoimzation and configuration.

At the next step, you can specify precisely which tables, fields, indices, views you want to transfer to the PostgreSQL destination database. Just check/ uncheck the box in front of each database object you want to convert.

Customize general database/ tables settings. Or set up a particular table , field, index individually when migrating data from SQL Server to PostgreSQL.

Check out our articles about Custoimzation and configuration. for detailed information.

The screenshot below sums up general features available in DBConvert software solutions.

4. Detection of potential database migration issues. Errors and Warnings

The database typically constrains certain relations on the data that cannot be violated. On the customization step, a smart error checker verifies all possible Data integrity and Referential integrity issues and highlights them, if any, before performing a migration.

DBConvert software to default tries to automatically map database types from the source SQL Server database to the closest equivalent of the target PostgreSQL database types. But you can manually change data types for the whole database globally with "Global mapping" or individually for each field.

Check out Smart error checker. Errors and Warnings for more information.

5. Execution. The final stage of data migration from SQL Server to PostgreSQL

Once you configure source and destination databases for migration in the previous steps, you can start the actual conversion or synchronization process.

Click the "Commit" button to start conversion. Also, here, you can monitor the migtation/ synchronization process.

Optionally save connection settings and configuration parameters into the session file to schedule the launching of sync or migration jobs regularly.

Execution step of DBConvert products

Read more about execution stage available options.

Command line mode

Previously saved sessions can be passed as parameters to Command-Line DBConvert Client. A session keeps SQL Server source and PostgreSQL target database connection settings with other specified options.

Example: C:\Program Files\DBConvert\mssql2postgresqlPro\mssql2postgresqlPro_Cons.exe /Session:"Session_Name"

NOTE: First, you have to run the software in GUI mode to create a session file with initial parameters.

Built-in scheduler.

Our applications come with a built-in scheduler to run database migration and sync jobs at specified times. Just set the scheduled date and time to execute job sessions automatically.

DBConvert screenshot

Highlights

Requirements

  • Necessary privileges to write into database on the target SQL Server (this requirement is optional as there is an option to overcome the restrictions using dump file)
  • Necessary privileges to write into database on the target PostgreSQL server (this requirement is optional as there is an option to overcome the restrictions using dump file or PHP Script)