SQL and more with KRUTI: SQL , Lift up your heads for the cloud

In my journey with Azure SQL Server I am often asked.

1) Why should I move to cloud ?
2) Which model should I go for ?
3) What do I need to do if my SQL server is on cloud ?

While all the answers are out there in many cloud forums and websites people often tend to forget the basics. They are What,When,Where, How and obviously the big Y.So lets address them one by one.

Why Should I move to Cloud?

Was any Y ever answered in a one liner ?
Weren't they always in the answer in brief section ? 😏

What : Cloud in literal terms is a layer, a carrier of your services.
It can provide you Hardware to access if you like (Infrastructure as a service/ IAAS),
It can provide you a mix of both Hardware and Software to some extent (Platform as a service/PAAS)
or It can provide only the Software for you to work with (Software as a Service/SAAS)

When : You can choose to move to cloud after having discussed with your stakeholders and decision makers keeping in mind your end customers. It always helps to do your homework before the TESTS and not during the TESTS (Yes your DEV, UAT, SIT,Pre-Prod and Prod servers/apps) . And by that I mean familiarizing yourself with the pros and cons of the technology you will choose or propose to your clients.

Where : As a consumer of Azure services myself I would say Microsoft Azure. But you all must be aware, that cloud is everywhere. So you can choose from lot of vendors once you decide the model. Your vendor SLA's and prices essentially governs your choice.

How : There are a variety of tools you can choose from, references to which are at the end of this section. I want to ensure I help you in your homework.

Why : The key lies in the amount of control you would like to retain for the hardware, software, applications and most importantly the peace of mind.Not just for your clients but your bosses,co-workers, employees and you. Here are a few points which highlight the why's

One should move to cloud if one can see the cloud and you are visionary (That's my personal thought I know some may think and see differently 😉 No awards or perks for anyone who wishes to debate)
One should choose cloud if their hardware and software needs monitoring and control 24*7.
One should move to cloud as you never know, when calamity strikes.
And if and when it does you cannot be expected to think of your office and clients instead of your own safety and your loved ones well-being.
One should move to cloud if you intend to be happy, along with making your clients happy and your workers happy.

I'm hoping after this you will be advancing to cloud. Let me help you in understanding the next steps

Which model should I go for?

The extent of management and administration will vary based on the model you choose (IAAS/PAAS/SAAS). This will also matter in the amount of labor hours and cost an organization saves in genera. The saved resources can be utilized to focus on upgrading and up scaling to something bigger, better and faster efficiently.

You may have come across the below diagram many a times

To make simpler than it already is here is how you choose

IAAS -> Infrastructure as a Service
1) Do you want to be in complete control of your entire machine (CPU, Memory, RAM, Disks, I/O)
2)Do you want to be in complete charge of what goes in and out of the machine (CPU, Memory, RAM, Disks, I/O) ?
3) Are you not OK sharing any Software or controllable Hardware?
If the answer is yes. Your model is IAAS.

Clearly since only you can go in and out of the machine only you can install or uninstall products thus managing the applications deployed on the machine.
The provider is responsible to ensure at all times, you have the Machine up and running.
You will not loose your Configuration of the Machine

PAAS -> Platform as a Service
1) Do you want to be in control of the platform but not pay for the whole machine (CPU,Memory,RAM,Disks,I/O) ?
2) Do you want someone to ensure your platform is up and running all the time. Irrespective of your machine,where precisely and how they get deployed?

3) Are you OK with sharing the machines as long as your applications, its design and data are accessible to only to you ?

If the answer is yes. Your model is PAAS.

Clearly you are on a shared hardware you may not be be able to set the CPU,Memory,RAM,I/O directly.
But through a careful choice of options you can control the amount of the hardware you can select from.
The provider is responsible to ensure your Platform is up and running. Even if the underlying Machine breaks down.
You will not loose your Design and Data for the applications

SAAS -> Software as a Service
1) Do you want to be in control of the service but not pay for the whole machine or the products installed on it (CPU,Memory,RAM,I/O + Applications)
2) Are you OK sharing but you want to ensure the services are up all the time ?
If the answer is yes. Your model is SAAS.

Clearly you are on a shared hardware you may not be be able to set the CPU,Memory,RAM,I/O directly.
Neither can you choose the way the platform is designed or the way data is stored.
The provider is responsible to ensure your Services are running at all times. Even if the underlying Machine breaks down or the Platform changes.
You will not loose your access to the Service.

What do I need to do if my SQL server is on cloud?

You need to do precisely what you are not paying for

And be in control of what your cloud provider does for you.

IAAS: If you paying only for the Machine, you manage the platform & applications on it

(Provider will also have access to ensure continuity of your access to the machine)

PAAS: If you are paying for the Platform, you manage the design of your application, data and who access it.

(Provider will also have access to ensure continuity of your access to the platform)

SAAS: If you are paying for the Services, you manage on the end users who access/avail it

(Provider will also have access to ensure continuity of your access to the services)

Enough talking lets get doing :)So here are the links for how to and a further reads

When referencing the below links ensure you are checking for the latest update dates. You cannot expect things not to change in the Azure world. Ensure you check when the page was last modified before you implement the steps and procedures. Never forget to thank the ones you find helpful.