For years Teradata was an MPP database leader, and a go-to database for large data footprints. However, weighed by its legacy, Teradata could not bring granular just-in-time elasticity control to their platform. Because of this, Snowflake is replacing many Teradata deployments, providing cost-efficient, low touch, and high throughput MPP in the cloud. However, migrating from Teradata to snowflake is not a project you just “throw bodies at," like traditional Systems Integrators would recommend.

Taking on a Teradata migration to Snowflake requires pattern-based automated accelerators which are made for such a task. In our Teradata to Snowflake migrations, Intricity has developed such accelerators which massively reduce the labor and time to completion. By breaking up the accelerators into nimble automations, Intricity’s migration specialists can iterate through the complexities between the two platforms in a manageable consulting services engagement.


Strategic Analysis of Complexity

This engagement starts with a short strategic assessment of the migration effort, which includes a detailed scan of the client's current Teradata footprint and any associated Integration to categorize levels of complexity and pattern reuse. This produces Empirical Counts and Complexity Levels for converting:

    • Databases
    • Tables
    • Views
    • Stored Procedures
    • Functions
    • ETL/ELT Jobs
    • Orchestration Jobs
    • Shell Scripts

Additionally, Intricity reviews downstream impacts on analytical applications and information consumption needs. This work effort is encapsulated in a short one-week engagement. The end result is a planned and fully costed migration along with a detailed breakdown of the complexity levels to be migrated.

With this effort empirically defined Intricity can effectively provide consultative options on whether the Teradata migration effort should take a “lift and shift” approach, a phased migration, or a re-architecting of the solution architecture. Having this knowledge is key to reducing the risk and costs as much as possible, as well as maximize the benefits of cloud computing with Snowflake.


Migration Factory

Code Conversion Pattern Expanded NEW Version 2

Once the strategic analysis has completed, the development team sets up a migration factory by separating the identified patterns and prioritizing them. Then Intricity iterates through the prioritized patterns with its automated accelerators through a controlled migration process. This process ensures that both patterns as well conversion code are continuously updating as the migration proceeds, thus the speed of conversion accelerates over the course of the project.

Intricity conducts this process for ETL Packages, Shell Scripts, Tables, Views, Stored Procedures, and Functions. At the end of this migration process your organization emerges with a completed conversion to Snowflake, enjoying all the operational benefits of just-in-time cloud elasticity for your data integration and warehousing.


Engaging Intricity

To review the Intricity migration from Teradata to Snowflake in more detail reach out to review your specific use case.