Click here to Skip to main content
15,889,992 members
Articles / Hosted Services / AWS
Technical Blog

Migrating your SQL Server Workloads to PostgreSQL

Rate me:
Please Sign up or sign in to vote.
4.09/5 (3 votes)
22 Sep 2019CPOL2 min read 4.7K   2   3
This multi-part article series discuss migrating your databases, applications and services from SQL Server to PostgreSQL and discusses all the important information you need to be aware of, before beginning a migration project..

Introduction 

This multi-part article series discuss migrating your databases, applications and services from SQL Server to PostgreSQL and discusses all the important information you need to be aware of, before beginning a migration project.

I’ve had the opportunity of architecting such a large migration involving a number of big SQL Server Instances (with over 100 databases in total) to AWS Aurora PostgreSQL with a total size of over 20 terabytes. I’m sharing my experience here.

While I have taken every effort to make sure that the information presented here is accurate; things might have changed, features that were not supported in older versions might be supported in newer versions, etc. If you find something inaccurate, misleading or grossly wrong, please feel free to leave a comment with the details and the links to support your claims, I’d be glad to update the article with the correct information.

About the Article Series

Part 1

The first article in the series discusses:

  • Introduction to Open Source Software, its advantages and disadvantages
  • Moving from Licensed software to Open Source software
  • Basics and the history of Microsoft SQL Server and PostgreSQL
  • Choosing the right PostgreSQL Edition and Version for your needs
  • Production, Development & Testing Workloads
  • On-Premise vs Cloud comparison

Part 2

The second article discusses:

  • In-depth comparison of SQL Server and PostgreSQL
  • Concurrency Control
  • Database Structure comparison
  • Feature comparison
  • Data Type Mapping
  • Built-In Functions and Operators
  • SQL Syntax differences
  • Areas where PostgreSQL has an edge
  • Areas where SQL Server has an edge

Part 3

The third article discusses:

  • The actual migration process
  • Schema migration
  • Data migration
  • ETL/ELT Considerations
  • Reporting Platforms
  • Analytics Platforms
  • Scheduling Options
  • Application/Services Migration

Part 4

The fourth and the last article in the series discusses:

  • Maintenance and Monitoring
  • High Availability, Load Balancing, and Replication
  • Environment Stabilization via Parallel Deployment

Article Links

The post Migrating your SQL Server Workloads to PostgreSQL appeared first on The Developer Space.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



Comments and Discussions

 
GeneralMy vote of 1 Pin
codeprojec1t22-Jun-20 2:18
codeprojec1t22-Jun-20 2:18 
PraiseVery nice Pin
RickZeeland22-Sep-19 23:16
mveRickZeeland22-Sep-19 23:16 
GeneralRe: Very nice Pin
Shameel23-Sep-19 0:24
professionalShameel23-Sep-19 0:24 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.