A Pharmacy Benefits Manager serving 27+ million members was experiencing serious performance and reliability issues with their Teradata data warehouse supporting mission-critical app.
Providing access to centralized pharmacy claims information is what Pharmacy Benefits Managers (PBMs) do; it’s what empowers them to help both pharmacies and insurers identify fraud, waste, and other potential savings.
In other words, their data is their value. So, when a certain PBM (serving 27+ million members throughout the U.S.) found themselves facing increasingly destabilizing performance issues with their on-prem Teradata data warehouse, finding a solution was a top priority.
One of the company’s most important business-critical applications was especially responsible for hampering the performance of other systems, but there were few options to remediate the problem without limiting access.
Ultimately, it was clear that the PBM’s existing systems couldn’t scale to meet their needs. With their Teradata contract coming up for renewal, they were eager to invest in a next-generation data warehouse platform, with a modern, cloud-based architecture. They became especially interested in Snowflake — not only because it could resolve their multi-tenancy issues and do what their existing system did more efficiently, but also because it provided the best support for new use cases, such as Data Sharing, that could potentially unlock new revenue streams.
However, they also understood that enterprise-scale data warehouse migrations bring complexity and risk. Knowing they needed deep expertise around Snowflake, they turned to phData’s team of specialists to map a path to a modern cloud-based platform with the ability to support both current and future needs.
Ultimately, the PBM is now positioned not only to scale their data warehouse with far better performance, but to support
innovative new ways of monetizing the value of their data.
As one of our solutions architects put it: anyone migrating to Snowflake from an on-prem data warehouse knows there is
“no easy button” to make it happen. But when you make the jump — and you do it with Snowflake-specific data ingestion,
architecture, and operational best practices in mind — the results will speak for themselves.