moving a DB shop to the cloud..

Let’s suppose your management decides to let the main SQL Server go to a cloud environment. What are the possible scenarios questions you will be asking or hoping to provide to be documented for 2-way reference.. what else can you think of other than the below?
How many drives and how big? (Data/Log)
Drives – what RAID config?
How often the backups should happen for each db(FULL,TLog etc)
Performance monitoring.
Tech/Admin Contacts
High Availability/Disaster Recover options/policy
Any custom resources: (examples: extra 2 CPU Cores 8am-noon every Monday and Wednesday etc)
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

PadawanDBAOperational DBACommented:
The cloud platform matters.  Are you talking about moving to Azure or AWS or something completely different?  If it's Azure, are you talking about an Azure VM with SQL Server installed on it or migrating the databases into Azure SQL Databases?
25112Author Commented:
I am sorry I was not totally aware abt Azure. I thought they will just move the databases to a SQL ____ 92012 or 2014) that you specify and we will connect to it through SSMS? how is Azure different than 2012/2014 versions?
PadawanDBAOperational DBACommented:
So it's not really different in so far as what it does as compared to those versions.  If you are using Azure SQL Databases, there are some datatypes not supported and some other requirements around prepping your databases for migration.  You connect to the database, and have no direct administrative control/visibility into the instance level diagnostics/configurations.  If you are in a VM that's hosted in Azure and you install SQL Server in that, there are no aforementioned restrictions and you have complete control over the instance configuration/diagnostics - however minimal control over the VMs performance in Azure.  If you're going with the second, I can link you to one of my blog posts around best practices for deploying in that scenario (especially around achieving as-close-as-possible-to-linear scaling of storage IOPS/throughput).
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

Rob GMicrosoft Systems EngineerCommented:
I would ask what the cost of bandwidth is.. Because if you don't have a fat pipe, and the WAN to support the amount of bandwidth this could create, i wouldn't bother.. Most people who go LAN to Cloud don't realize just how much more expensive it is in the long run.
25112Author Commented:
>>If you're going with the second
yes please
PadawanDBAOperational DBACommented:

Just to underscore a subtle point in this post: I did this research because a client used software RAID inside of windows to configure their disk - never, ever, ever do that in Azure =)  Also, try and price out one of the VM classes that gives you 16 disks.  You can go up to 1TB max on each (at least that's what it was when I wrote this... the limits and features and classes of VMs you can get are constantly changing - usually in favor of more resources/higher caps), and you only get charged for what you use (you may want to clarify with MS if that means the provisioned drive sizes carved out of the storage pools or the actual data stored).

edit: also the bandwidth point is a very good one.  however, it brings up the additional concern of your ability to sustain higher latency on data access (as you will be transferring the data over WAN).  I'm not going to lie, usually the move to cloud involves moving an entire application platform to the cloud (which also solves the bandwidth cost issue) - or a function such as reporting, with high inbound traffic, which you don't have to pay for, and low outbound traffic.

edit part 2: also, to go into your initial question a little more.  if you're going with SQL Server in an Azure VM, you are going to want to monitor it and perform maintenance on it just like you would any other VM =)  You also administer it just like you would any other SQL Instance, so you build out your availability options (mirroring, log shipping, replication or alwaysOn like you would for any SQL Environment)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
25112Author Commented:
Thank you!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.