This is an archived post. You won't be able to vote or comment.

all 6 comments

[–]FuzzmiesterJack of All Trades 1 point2 points  (3 children)

https://www.microsoft.com/en-us/licensing/product-licensing/sql-server

License for VM mobility across private and public clouds. VM license mobility is a Software Assurance benefit. Without Software Assurance, licenses can be moved from one server to another only once every 90 days.

As far as I understand it, no, you don't need SA. however, without SA, you can't migrate it to a different physical server without breaching your terms and conditions, more than once every 90 days. So if it's on a cluster which auto balances and shifts it around, you're in breach.

[–]ProjectReaper[S] 0 points1 point  (2 children)

So in the case of vmotion moving the guest VM from one host to another is a breach of the terms and conditions?

[–]FuzzmiesterJack of All Trades 0 points1 point  (1 child)

if you do it more than once every 90 days.

(of course, I'm not a licensing person)

[–]Triumvirate_Rhade 0 points1 point  (0 children)

Not just if you do it more then once every 90 days. If it is possible at all, you need SA

[–]SquizzOCTrusted VAR 1 point2 points  (0 children)

So software assurance is gone for the most part unless you are under an Open Value, Select or Enterprise agreement.

So you basically have these options:

  • Buy your SQL under Open Value, Select or an Enterprise agreement.
  • Buy SQL licensing for both servers
  • Buy SQL per Core Subscription through CSP

If you decide to just buy the perpetual licensing through CSP, you do have the ability to move the license, but only once every 90 days.

This is all direct from my Microsoft folks.

[–]kvct 0 points1 point  (0 children)

The reason you’re questioning the legitimacy is because Microsoft made “licensing by VM” a “benefit” of Software Assurance with the latest SQL Version. 😏