by: Mike Waas
How Replatforming to a Cloud Data Warehouse Could End Your Career — TDWI
This article appeared on TDWI.org
The pandemic has been a wake-up call of enormous proportions for many IT departments. To compete effectively in a post-COVID-19 economy, companies realized they needed to embrace the cloud, urgently. How they lay the foundation in the cloud will matter for many years to come. As always, data is at the heart of the matter.
The most critical first step is to devise and implement a replatforming strategy from the on-premises enterprise data warehouse (EDW) to a counterpart in the cloud including every department connected to the EDW and every major revenue source that depends on it. Its importance cannot possibly be overstated.
If IT executes well on the replatforming strategy, they will accelerate revenue, reduce cost, and ensure they achieve compliance. If they execute poorly, replatforming may turn into a quagmire — and end careers. Learning from others’ mistakes in this space offers a few vital lessons. Let’s examine a few mistakes often made by IT leaders and how to overcome each one of them.
Mistake #1: Not Knowing What’s in Your EDW
Few enterprise IT executives have sufficient clarity when it comes to the operations of their on-premises EDW. Over the years, more business users started tapping the EDW for its incredibly valuable data, so it’s no surprise the system has become home to a myriad of workloads. Some are well-designed although others reflect the ad hoc nature of the projects from which they originated.
Many service providers offer assessments that promise to help. However, most assessments stop at the number of statements run each day and the total volume of data on disk. This rather primitive level of insight does not help much when preparing for a migration. If anything, it may provide a false sense of security up-front and lead to disaster down the road. Read the full article here.