MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.47k forks source link

PAYG vs BYOL benefit. #30695

Closed dcallagh closed 5 years ago

dcallagh commented 5 years ago

It states here that BYOL becomes more cost effective after 10 months, however if i purchase an 8 core enterprise license + SA the cost is $113,000 excluding VM costs, the cost to run a PAYG enterprise for 36 months on this platform is roughly $108,000 excluding VM costs. Struggling to make a case for BYOL in this scenario. Is there something I am missing?


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

VikasPullagura-MSFT commented 5 years ago

@dcallagh Thanks for the question! We are investigating and will update you shortly.

mimckitt commented 5 years ago

@dcallagh can you share some screenshots of the calculations you are running so I can get a better understanding?

It is cheaper to use your own licenses in some cases. But it is not tens of thousands of dollars cheaper as you are seeing. We state the average savings in the doc as you likely already found image

There is also a lot of consideration you need to put into the size of your VM to make sure you are not over paying.

mimckitt commented 5 years ago

Any update?

dcallagh commented 5 years ago

Hi all. The issue pertains to the section specifically on byol sql licenses which states 10 months is the payback period for build v payg. This is wrong as I compared SQL license only costs for 8 cores payg and byol. Byol 8 core is $113k au ex gst. One 8 core  payg server excluding vm costs is @36k per annum. So 3 years before byol can even hope to compare. If we add a passive dr aoag server of the same size that's $72k per annum which leaves byol far short of even parity. And recall the passive server need not be 8 core and so payg could be less than 72k per annum. Leaving byol more expensive for far longer than 10 months.Sent from my Samsung Galaxy smartphone. -------- Original message --------From: Micah notifications@github.com Date: 10/5/19 2:39 am (GMT+10:00) To: MicrosoftDocs/azure-docs azure-docs@noreply.github.com Cc: dcallagh dcallagh@iname.com, Mention mention@noreply.github.com Subject: Re: [MicrosoftDocs/azure-docs] PAYG vs BYOL benefit. (#30695) Any update?

—You are receiving this because you were mentioned.Reply to this email directly, view it on GitHub, or mute the thread. [ { "@context": "http://schema.org", "@type": "EmailMessage", "potentialAction": { "@type": "ViewAction", "target": "https://github.com/MicrosoftDocs/azure-docs/issues/30695#issuecomment-490977901", "url": "https://github.com/MicrosoftDocs/azure-docs/issues/30695#issuecomment-490977901", "name": "View Issue" }, "description": "View this Issue on GitHub", "publisher": { "@type": "Organization", "name": "GitHub", "url": "https://github.com" } } ]

mimckitt commented 5 years ago

@dcallagh thanks for the reply and the details.

@MashaMSFT can you take a look at this one? Might make sense to have some more information about the savings and how they are calculated integrated into this doc.

MashaMSFT commented 5 years ago

Hi @dcallagh and @MicahMcKittrick-MSFT , thanks for bringing this to our attention :) Let me look into this a bit further. Thanks!

MashaMSFT commented 5 years ago

Hi @dcallegh, just wanted to reach out and let you know I'm still looking into this, and I appreciate your patience :) Thanks!

MashaMSFT commented 5 years ago

Hi @dcallegh, thanks again for your patience, I am continuing to research this for you.

Thanks!

MashaMSFT commented 5 years ago

Hi @dcallegh, thanks for bringing this to our attention! We've decided to remove this part of the document as it doesn't cover every scenario and can be confusing. Instead, we recommend using the Azure Hybrid Benefit calculator to determine the most cost effective price, which can be found here: Azure Hybrid Benefit

I hope that helps and please let us know if we can be of further assistance? If not, we will proceed with closing out this Git Issue in a few business days.

Thanks! Masha from the SQL Docs team

MashaMSFT commented 5 years ago

please-close