Jul 03, 2018 - 12:25 AM
If an environment is occasionally used for production then you can't license it using MSDN/VS licenses. It has to be dedicated to Dev/Test. Strongly recommend that you don't use a Dev/Test cluster for DR. Production data should never touch Dev/Test, other than for the purposes of testing your app, and even then you must discard the processed data at the end of the test. It can't be copied back to Production.
If your max version is 2014 or higher you need to have Software Assurance coverage on the SQL core licenses to get "free" failover (or an Active/Passive cluster)
The Passive host must be truly passive - if you query it at the same time as the Active you have to license it. All it can do is sit there syncing with the active and being backed up. You can't even use it to generate batch reports.
There's a bunch of other considerations around SQL Server licensing - if you'd like to learn more I recommend you take a look at our SQL Server training via LISA
Jul 03, 2018 - 01:40 AM
we are working with several version: 2005, 2008, 2012 and 2016.
The license is for the whole esx hosts (physical server), licensed per core, we have Sw assurance.
The DR environment is used for test/dev but on dedicated esx. We have to isolate esx and make them specific to SQL server in DR.
I will have a look to your training, I am interested.
Jul 03, 2018 - 03:07 AM
The issue that you have is that you can't mix Prod and MSDN/VS licensing on the same physical hardware. The specific wording is "(Production environments include...) Environments that are used for production at least some of the time, such a server that is rotated into production during peak periods of activity."
Source: Microsoft Product Terms, MSDN/VS Licensing Guide