Key considerations for moving a database to the public Cloud

Posted in: Technical Track

Businesses today are under constant pressure to “digitize” and “transform.” As IT professionals, we play a key role in contributing to transformation by doing it faster, cheaper, and better.

A move to the public cloud can play a significant role in making all of these things possible. Businesses are looking to the cloud to increase software velocity— meaning they can ship bug fixes and new product features several times per day, or even week, and stay ahead of their competition.

As the public cloud matures, it becomes easier to move data into the cloud. But should we? The answer may be yes—but I prefer to say “it depends.”

There are a lot of considerations to make before moving to the cloud:

  • Business considerations (like cost, or data retention.)
  • Technical considerations (like shared networks, or performance.)
  • Legal considerations (like geographic implications, or data sovereignty.)
  • Project considerations (like training, or data partner support.)

I gave this presentation at Cloud Expo 2016 in New York City, and it is especially helpful for those early on in the cloud adoption process. It will provide you with information and important considerations to think about in the beginning stages of a migration project.



What comes next?

The considerations you just learned about are only part of the first phase in a successful cloud migration project. Here is a proven five phase framework that our cloud experts follow to reduce risks and avoid costly mistakes associated with a cloud migration.







Want to talk with an expert? Schedule a call with our team to get the conversation started.

About the Author

Chris Presley loves order—making him a premier Microsoft SQL Server expert. Not only has he programmed and administered SQL Server, but he has also shared his expertise and passion with budding DBAs as SQL Server instructor at Conestoga College in Kitchener, Ontario. Drawing on his strong disaster-recovery skills, he monitors production environments to swiftly detect and resolve problems before they arise. A self-described adrenaline junkie, Chris likes tackling the biggest database problems and putting out the toughest fires—and hitting the road on his motorcycle.

No comments

Leave a Reply

Your email address will not be published. Required fields are marked *