Case Sensitivity Differences for SQL Server and PostgreSQL - SQL Server to Aurora PostgreSQL Migration Playbook
Services or capabilities described in Amazon Web Services documentation might vary by Region. To see the differences applicable to the China Regions, see Getting Started with Amazon Web Services in China.

Case Sensitivity Differences for SQL Server and PostgreSQL

Object name case sensitivity might be different for SQL Server and PostgreSQL. SQL Server names are depended on the used collection and can be either case sensitive or not. PostgreSQL names are case sensitive.

By default, Amazon Schema Conversion Tool (Amazon SCT) uses object name in lowercase for PostgreSQL. In most cases, you’ll want to use Amazon Database Migration Service transformations to change schema, table, and column names to lower case.

To have an uppercase name, you must place the objects names within doubles quotes. For example, to create a table named EMPLOYEES in uppercase in PostgreSQL, you should use the following:

CREATE TABLE "EMPLOYEES" (
  EMP_ID NUMERIC PRIMARY KEY,
  EMP_FULL_NAME VARCHAR(60) NOT NULL,
  AVG_SALARY NUMERIC NOT NULL);

The following command creates a table named employees in lowercase.

CREATE TABLE EMPLOYEES (
  EMP_ID NUMERIC PRIMARY KEY,
  EMP_FULL_NAME VARCHAR(60) NOT NULL,
  AVG_SALARY NUMERIC NOT NULL);

If you don’t use double quotes, PostgreSQL creates objects with lowercase names. Therefore, to create, query, or manipulate an uppercased or mixed object names, use double quotes.