# Panoply.io Destination Reference Panoply is a fully managed data warehouse service that will spin up an Amazon Redshift instance in just a few clicks. With Panoply, you can use your favorite analysis, SQL, and visualization tools just like you would if you were creating a Redshift data warehouse on your own. This guide serves as a reference for version 2 of Stitch’s Panoply destination. ## Details and features * [Stitch features](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#stitch-features) * [Destination details](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#destination-details) * [Pricing](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#pricing) ### Stitch features High-level details about Stitch’s implementation of Panoply, such as supported connection methods, availability on Stitch plans, etc. | **Release status


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | Released | | --- | --- | | **Stitch plan availability


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | All Stitch plans | | **Stitch supported regions


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** |

Operating regions determine the location of the resources Stitch uses to process your data. [Learn more](https://help.qlik.com/en-US/stitch/security/supported-data-pipeline-regions). | | **Supported versions


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | Not applicable | | **Connect API availability


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Supported
the Success iconSupported**

This version of the Panoply destination can be created and managed using Stitch’s Connect API. [Learn more](https://help.qlik.com/en-US/stitch/developers/stitch-connect/api#destination-form-properties). | | **SSH connections


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Unsupported
the Remove iconNot supported**

Stitch does not support using SSH tunnels to connect to Panoply destinations. | | **SSL connections


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Supported
the Success iconSupported**

Stitch will attempt to use SSL to connect by default. No additional configuration is needed. | | **VPN connections


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Unsupported
the Remove iconNot supported**

Virtual Private Network (VPN) connections may be implemented as part of a Premium plan. Contact [Stitch Sales](https://www.stitchdata.com/contact/) for more info. | | **Static IP addresses


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Supported
the Success iconSupported**

This version of the Panoply destination has static IP addresses that can be whitelisted. | | **Default loading behavior


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Upsert**

**Note**: Append-Only loading will be used if all conditions for Upsert are not met. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior). | | **Nested structure support


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | **Unsupported**

the Remove icon

Unupported


Nested data structures will be flattened into relational objects. [Learn more](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--json-structures). | ### Destination details Details about the destination, including object names, table and column limits, reserved keywords, etc. **Note**: Exceeding the limits noted below will result in loading errors or rejected data. | **Maximum record size


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | 20MB | | --- | --- | | **Table name length


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | 127 characters | | **Column name length


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | 115 characters | | **Maximum columns per table


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | 1,600 | | **Maximum table size


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | None | | **Maximum tables per database


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | 100,000 | | **Case sensitivity


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | Insensitive | | **Reserved keywords


[the Help icon](https://help.qlik.com/en-US/stitch/destinations/panoply/reference)** | Refer to the [Reserved keywords documentation](https://help.qlik.com/en-US/stitch/replication/loading/reserved-keywords#panoply-v2-reserved-keywords). | ### Pricing Pricing varies from plan to plan, but every Panoply plan includes: * Unlimited queries * Unlimited user accounts * Automatic maintenance, vacuuming, and backups Panoply charges based on the amount of data stored and offers several plan options for your needs. [Refer to their pricing page for more information](https://panoply.io/pricing/). ## Replication * [Replication process overview](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication-process-overview) * [Loading behavior](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#loading-behavior) * [Primary Keys](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication--primary-keys) * [Incompatible sources](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication--incompatible-sources) ### Replication process overview A Stitch replication job consists of three stages: * [Step 1: Data extraction](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication--data-extraction) * [Step 2: Preparation](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication--stitch-internal-pipeline) * [Step 3: Loading](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#replication--loading) #### Step 1: Data extraction Stitch requests and extracts data from a data source. Refer to the [System overview guide](https://help.qlik.com/en-US/stitch/getting-started/basic-concepts-system-overview#system-architecture--extraction) for a more detailed explanation of the Extraction phase. #### Step 2: Preparation During this phase, the extracted data is buffered in Stitch’s durable, highly available internal data pipeline and readied for loading. Refer to the [System overview guide](https://help.qlik.com/en-US/stitch/getting-started/basic-concepts-system-overview#system-architecture--preparing) for a more detailed explanation of the Preparation phase. #### Step 3: Loading Stitch loads the data into Panoply. ### Loading behavior By default, Stitch will use **Upsert loading** when loading data into Panoply. If the conditions for Upsert loading aren’t met, data will be loaded using Append-Only loading. Refer to the [Understanding loading behavior guide](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-behavior) for more info and examples. ### Primary Keys Stitch requires Primary Keys to de-dupe incrementally replicated data. To ensure Primary Key data is available, Stitch creates a `primary_keys` [table comment](https://docs.aws.amazon.com/redshift/latest/dg/r_COMMENT.html). The comment is an array of strings that contain the names of the Primary Key columns for the table. For example: A table comment for a table with a single Primary Key: ``` '{"primary_keys":["id"]}' ``` And a table comment for a table with a composite Primary Key: ``` '{"primary_keys":["event_id","created_at"]}' ``` **Note**: Removing or incorrectly altering Primary Key table comments can lead to replication issues. ### Incompatible sources The Panoply destination has reported incompatibilities with some of Stitch's integrations. Refer to the table below for more info. | **Integration** | **Version** | **Level** | **Reason** | | --- | --- | --- | --- | | MongoDB | ANY | the Warning 2 icon

This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Panoply’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). | | MongoDB Atlas | v1 | the Warning 2 icon

This destination/integration combination is sometimes incompatible. | Flattening nested JSON structures may result in tables with columns that exceed Panoply’s 1,600 column limit. [Learn more](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). | See all [destination and integration incompatibilities.](https://help.qlik.com/en-US/stitch/destinations/destination-integration-compatibility) ## Transformations * [System tables and columns](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--system-tables-columns) * [Data typing](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--data-typing) * [JSON structures](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--json-structures) * [Column names](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--column-naming) * [Timezones](https://help.qlik.com/en-US/stitch/destinations/panoply/reference#transformations--timezones) ### System tables and columns Stitch will create the following tables in each integration’s dataset: * [_sdc_rejected](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/rejected-records-system-table) Additionally, Stitch will insert [system columns](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns) (prepended with `_sdc`) into each table. ### Data typing Stitch converts data types only where needed to ensure the data is accepted by Panoply. In the table below are the data types Stitch supports for Panoply destinations, and the Stitch types they map to. * **Stitch type:** The Stitch data type the source type was mapped to. During the Extraction and Preparing phases, Stitch identifies the data type in the source and then maps it to a common Stitch data type. * **Destination type:** The destination-compatible data type the Stitch type maps to. This is the data type Stitch will use to store data in Panoply. * **Notes:** Details about the data type and/or its allowed values in the destination, if available. If a range is available, values that exceed the noted range will be [rejected by Panoply](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/rejected-records-system-table). | **Stitch type** | **Destination type** | **Notes** | | --- | --- | --- | | BIGINT | [BIGINT](https://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html#r_Numeric_types201-integer-types) | | | BOOLEAN | [BOOLEAN](https://docs.aws.amazon.com/redshift/latest/dg/r_Boolean_type.html) | | | DATE | [TIMESTAMP](https://docs.aws.amazon.com/redshift/latest/dg/r_Datetime_types.html#r_Datetime_types-timestamp) | | | DOUBLE | [DOUBLE](https://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html#r_Numeric_types201-floating-point-types) | | | FLOAT | [DOUBLE](https://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html#r_Numeric_types201-floating-point-types) | | | INTEGER | [INTEGER](https://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html#r_Numeric_types201-integer-types) | | | NUMBER | [DECIMAL](https://docs.aws.amazon.com/redshift/latest/dg/r_Numeric_types201.html#r_Numeric_types201-decimal-or-numeric-type) | | | STRING | [STRING](https://docs.aws.amazon.com/redshift/latest/dg/r_Character_types.html#r_Character_types-varchar-or-character-varying) | | ### JSON structures Panoply destinations don’t have native support for nested data structures. To ensure nested data can be loaded, Stitch will flatten objects and arrays into columns and subtables, respectively. For more info and examples, refer to the [Handling nested data structures guide](https://help.qlik.com/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures). ### Column names Column names in Panoply: * Must contain only letters (a-z, A-Z), numbers (0-9), or underscores (`_`) * Must begin with a letter * Must be less than the maximum length of 115 characters. Columns that exceed this limit will be [rejected by Panoply](https://help.qlik.com/en-US/stitch/replication/loading/system-tables-columns/rejected-records-system-table). * Must not be prefixed or suffixed with any of [Panoply’s or Stitch’s reserved keyword prefixes or suffixes](https://help.qlik.com/en-US/stitch/replication/loading/reserved-keywords#panoply-v2-reserved-keywords) Stitch will perform the following transformations to ensure column names [adhere to the rules imposed by Panoply](https://docs.aws.amazon.com/redshift/latest/dg/r_names.html): | **Transformation** | **Source column** | **Destination column** | | --- | --- | --- | | Convert uppercase and mixed case to lowercase | `CuStOmErId` or `CUSTOMERID` | `customerid` | | Remove special characters | `customer#id` or `!CuStOMerID` | `customerid` and `customerid` | | Remove non-letter leading characters | `4customerid` or `_customerid` | `customerid` | ### Timezones Panoply will store the value as `TIMESTAMP WITHOUT TIMEZONE`. In Panoply, this data is stored without timezone information and expressed as UTC. ## Compare destinations **Not sure if Panoply is the data warehouse for you?** Check out the [Choosing a Stitch Destination](https://help.qlik.com/en-US/stitch/destinations/choosing-a-stitch-destination) guide to compare each of Stitch’s destination offerings.