Craft a Cloud Strategy for the Enterprise Database

You want to leverage cloud deployments to reduce management costs, convert Capex to Opex, and enable scale on demand – all while only paying for resources when used.
Enterprise database licensing, deployment, and maintenance are among the most complex and expensive activities in IT.
Not all databases present a use case for a cloud deployment.
The effort required to re-platform enterprise systems for the cloud can erode perceived savings.
IT may not have the skills to deploy, integrate, and support enterprise systems in the cloud.

Our Advice

Critical Insight

Don’t focus on whether the cloud is ready for the database – identify whether each database workload is ready for the cloud.
Identify database workloads to move to the cloud via a holistic cloud strategy; avoid an ad hoc approach that’s more expensive, time-consuming, and can leave you with blind spots.
Look before you leap; identify risks and mitigation strategies associated with moving the enterprise database to the cloud.
Vendors will be much more tightly integrated into your ability to deliver services. Review vendor best practices, and move from ad hoc vendor management to a defined process.

Impact and Result

Break down the cloud strategy into digestible, concrete steps.
Identify and mitigate risks to your database in a cloud computing environment before you migrate.
Develop a consistent process for vendor management and database provisioning.

Craft a Cloud Strategy for the Enterprise Database Research & Tools

Start here – read the Executive Brief

Read our concise Executive Brief to find out why you should craft a cloud strategy for the enterprise database, review Info-Tech’s methodology, and understand the four ways we can support you in completing this project.

Craft a Cloud Strategy for the Enterprise Database – Executive Brief

1. Review the value opportunity for moving the database to the cloud

Document drivers and current cloud deployments in the enterprise. Select database workloads that are good candidates for a pilot deployment.

2. Document and mitigate cloud database risks

Identify risks and mitigation strategies, and develop a mitigation roadmap.

3. Complete the cloud database strategy

Create processes to make cloud database provisioning repeatable. Communicate the strategy to stakeholders.

About Info-Tech

Info-Tech Research Group is the world’s fastest-growing information technology research and advisory company, proudly serving over 30,000 IT professionals.

We produce unbiased and highly relevant research to help CIOs and IT leaders make strategic, timely, and well-informed decisions. We partner closely with IT teams to provide everything they need, from actionable tools to analyst guidance, ensuring they deliver measurable results for their organizations.

What Is a Blueprint?

A blueprint is designed to be a roadmap, containing a methodology and the tools and templates you need to solve your IT problems.

Each blueprint can be accompanied by a Guided Implementation that provides you access to our world-class analysts to help you get through the project.

Table of Contents

Need Extra Help?
Speak With An Analyst

Get the help you need in this 3-phase advisory process. You'll receive 9 touchpoints with our researchers, all included in your membership.

Guided Implementation 1: Review the value opportunity for moving the database to the cloud

Call 1: Review project drivers, existing deployments and initiatives, and current processes; discuss cloud deployment options.
Call 2: Review potential use cases for the database in the cloud.
Call 3: Complete the readiness-value exercise.

Guided Implementation 2: Document and mitigate cloud database risks

Call 1: Review project risks and develop a risk register for all workloads. Assess risk impact.
Call 2: Look back over project risks. Identify mitigation strategies to rightsize project risks.
Call 3: Score mitigation strategies, run a tabletop exercise, and create a roadmap.

Guided Implementation 3: Complete the cloud database strategy

Call 1: Review the structure of your requirements gathering process. Discuss potential vendors.
Call 2: Develop performance metrics based on vendor requirements, value opportunities, and risks.
Call 3: Review the charter and executive presentation.

Authors

Darin Stahl

Frank Trovato

Andrew Sharp

Contributors

David Linthicum, SVP, Cloud Technology Partners
Richard Thipe, Senior Architect, Transnet Freight Rail
Sphamandla Duma, Data Architect, Transnet Freight Rail
David Rahbany, Director of Enterprise IT Infrastructure
Lloyd Brathwaite, IT Infrastructure Manager
Brad Cambrey, Manager of Information Technologies, BC Office of the Ombudsperson
1 anonymous contributor