Amazon Redshift: Best practices for migration

Amazon Redshift is a ‘fully managed, petabyte-scale data warehouse service’ hosted in the cloud and delivered by Amazon Web Services (AWS). One of the key features of Amazon Redshift is efficient storage and optimum query performance through a combination of massively parallel processing and columnar data storage.

If you’re planning to migrate to Amazon Redshift, here’s our guide to make the process simple.

THE MIGRATION PROCESS

Pre-migration

Consider the following questions while you prepare for AWS migration:

  • Clear vision for your business: You should understand the business and the existing business logics involved in data conversion to build an effective data warehouse on Redshift.
  • Volume & Velocity. Do a volumetric analysis on the hot and cold data in the existing data warehouse. System. We have many migration tools available to move huge volume of data from on-premises to Redshift.
  • Objects involved: Make a note of all the objects which are developed in on premises and replicate the same to Redshift. As most existing SQL client applications will work on Redshift with minimal changes.

During migration

Few key things that you should keep in mind:

  • Key constrains: Redshift does not enforce unique, primary key and foreign key, so build your data warehouse logic in such a way that it avoids duplicate while loading data. Removing duplicates is very expensive operation. Check for the duplicates before loading it.
  • Sort key: Redshift does not support indexing, but it has something powerful called Sort key. Choosing the right sort key column and right type of sort key will give great query performance. Please note that, you cannot change the sort key after creating a table.
  • Distribution Key: Choose the right distribution key column and right type of distribution key to perform joins between tables. This will increase the join performance. Please note that, you cannot change the distributed key after creating a table.
  • Data type: Before creating a table be confident in choosing the data types of the column. we can add or drop the column but we cannot alter the data type of the column after creating a table. If you suspect the width of the column might increase in future do it while creating the table.

 Post migration

  • Monitor the environment using cloud-native monitoring tools. Lot of monitoring tools available for you to choose and use. They help to discover performance insights and utilize the cloud environment effectively.
  • Make the most of AWS Amazon Web Services provide highly available and reliable support for Redshift migration. Reach out to them with your queries/issues even after the migration is done.