Greenplum

Translation from Greenplum to Snowflake

Important Notice: Migration of Documentation Website

Please be advised that our documentation website is currently undergoing a migration to a new platform. To ensure you have access to the most up-to-date information, we kindly request that you visit our new documentation website located at:

Official Snowflake Snowconvert Documentation

For any immediate assistance or if you encounter any issues, please contact our support team at [email protected].

Thank you for your understanding.

Description

This section explains features exclusive to Greenplum.

For more information, please refer to CREATE TABLE the documentation.

Grammar Syntax

CREATE TABLE <table_name> ( 
  [ { <column_name> <data_type> [ ENCODING ( <storage_directive> [, ...] ) ]
] )
[ DISTRIBUTED BY ( <column> [<opclass>] [, ... ] ) 
    | DISTRIBUTED RANDOMLY
    | DISTRIBUTED REPLICATED ]

ENCODING

This syntax is not needed in Snowflake.

The compression encoding for a column. In Snowflake, defining ENCODING is unnecessary because it automatically handles data compression, unlike Greenplum, which could set up the encoding manually. For this reason, the ENCODING statement is removed during migration.

Grammar Syntax

ENCODING ( <storage_directive> [, ...] )

Sample Source

Input Code:

Greenplum

IN -> Greenplum_01.sql

CREATE TABLE TABLE1 (
   COL1 integer ENCODING (compresstype = quicklz, blocksize = 65536)
);

Output Code:

Snowflake

OUT -> Greenplum_01.sql

CREATE TABLE TABLE1 (
   COL1 integer
)
COMMENT = '{ "origin": "sf_sc", "name": "snowconvert", "version": {  "major": 0,  "minor": 0,  "patch": "0" }, "attributes": {  "component": "greenplum",  "convertedOn": "03/26/2025",  "domain": "test" }}'
;

DISTRIBUTED BY

This syntax is fully supported in Snowflake.

The DISTRIBUTED BY clause in Greenplum controls how table data is physically distributed across the system's segments. Meanwhile, CLUSTER BY is a subset of columns in a table (or expressions on a table) that are explicitly designated to co-locate the data in the table in the same micro-partitions.

Grammar Syntax

DISTRIBUTED BY ( <column> [<opclass>] [, ... ] )

Sample Source Patterns

Input Code:

Greenplum

IN -> Greenplum_02.sql

CREATE TABLE table1 (colum1 int, colum2 int, colum3 smallint, colum4 int )
DISTRIBUTED BY (colum1, colum2);

Output Code:

Snowflake

OUT -> Greenplum_02.sql

CREATE TABLE table1 (colum1 int, colum2 int, colum3 smallint, colum4 int )
--** SSC-FDM-GP0001 - THE PERFORMANCE OF THE CLUSTER BY MAY VARY COMPARED TO THE PERFORMANCE OF DISTRIBUTED BY **
CLUSTER BY (colum1, colum2)
COMMENT = '{ "origin": "sf_sc", "name": "snowconvert", "version": {  "major": 0,  "minor": 0,  "patch": "0" }, "attributes": {  "component": "greenplum",  "convertedOn": "03/26/2025",  "domain": "test" }}'
;

DISTRIBUTED RANDOMLY - REPLICATED

This syntax is not needed in Snowflake.

The DISTRIBUTED REPLICATED or DISTRIBUTED RANDOMLY clause in Greenplum controls how table data is physically distributed across the system's segments. As Snowflake automatically handles data storage, these options will be removed in the migration.

Grammar Syntax

DISTRIBUTED RANDOMLY | DISTRIBUTED REPLICATED

Sample Source Patterns

Input Code:

Greenplum

IN -> Greenplum_03.sql

CREATE TABLE table1 (colum1 int, colum2 int, colum3 smallint, colum4 int )
DISTRIBUTED RANDOMLY;

Output Code:

Snowflake

OUT -> Greenplum_03.sql

CREATE TABLE table1 (colum1 int, colum2 int, colum3 smallint, colum4 int )
COMMENT = '{ "origin": "sf_sc", "name": "snowconvert", "version": {  "major": 0,  "minor": 0,  "patch": "0" }, "attributes": {  "component": "greenplum",  "convertedOn": "03/26/2025",  "domain": "test" }}'
;

Related EWIs

1. SSC-FDM-GP0001: The performance of the CLUSTER BY may vary compared to the performance of Distributed By.