Minimizing Cloud cost9
June 20, 2016 by Kenneth Fisher
The cloud can be expensive. I had this hammered home the other day by a simple mistake. I’m currently working with Microsoft’s Azure platform and using one of the free credit options. I get a free $25 a month for a year and fortunately for me this put a limit on my on spending of that $25. I’d been playing around a bit, created and connected to a SQL Database, then decided to create my first Azure server. I created a server from a template, with SQL Server 2014 Enterprise installed. I connected to it, made sure it was working, and went to bed for the night. A couple of days later I checked on my account and was surprised to discover that my remaining $18 had disappeared that first night. I should point out that the server I used was less than $14 a month, not a day. Now for a company $18 in 12 hours might not be that big a deal, but it was a real shocker for me. I checked and discovered that the Enterprise license cost was ~$1.5 an hour for the VM I was using. Given what I know of Enterprise costs this shouldn’t have surprised me. I certainly should have known better. But it was a mistake. And without that limit it could have very quickly become a very costly one.
This got me thinking about ways to reduce/minimize costs. These are some general ideas since from what I can tell cloud billing is as complex as the tax codes and at that I have limited experience.
- If you aren’t using your VM, shut it down. You can do this manually, or with a powershell script or even at the push of a button
- Start small. Only create the machines you need and keep them to a minimum.
- Starting small will lead to some bottle necks. Feel free to bounce up and down as you need. There are some restrictions (size etc) when you move downwards, so be careful. Again this can be done manually or with powershell. Let’s say you need to do a high volume load. Bump your service tier, then once you are done, bump it back down again.
- And my personal favorite : Don’t install enterprise when you only need standard.
Remember that the whole point of the Cloud is the ability to use only the resources you need when you need them. If your company is only open 8-5 then why are you paying for an active VM from 5 to 9? In fact I’ve talked to people who have put jobs in place to turn their VMs on and off on a schedule. Resource management has always been important, but with the flexibility the cloud gives us, it has become even more so.
Category: Cloud, SQLServerPedia Syndication | Tags: Cloud
9 thoughts on “Minimizing Cloud cost”
Leave a Reply Cancel reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
There is also a difference between shutting down a VM from within the VM, vs. form the portal…not everyone catches that distinction 🙂
My favorite is Brent’s push button approach. Push the button as you come in in the morning and your VMs are up by the time you sit down. Push it again as you leave for the day and shut everything down. If I ever start a business based on the cloud that’s how I’m doing it.
Kenneth, Great thanks for simple but very useful advises
Thanks! I’m still a novice at this so simple is all I have right now. Hopefully that will change over the next few months/year.
Even if you shut down the VM, you still have to pay for the SQL Server license. We have a VM that is shut down all the time and is only powered on about 1 hour a month to install OS patches and then we shut it back down. The VM still costs over $500 per month because we’re billed for the SQL license.
*nod* Very good point. The cost calculations on cloud servers take in a HUGE number of variables. Still the cost is probably considerably lower since you have it shut down most of the time.
Look at Azure automation – this would allow you to write – (essentially powershell), a task that will run on a schedule to shut your machine down at say 7 in the evening, and start it at say 8 in the morning. That way you won’t forget.
Thanks. I’ll have to check that out. Sounds similar to what Brent used with his buttons.
[…] Size (dependent on edition), and Service Objective (also dependent on edition). These are going to dramatically affect your cost. When ready hit […]