SQL Server Failovers – Awkward Licencing Rules
SQL Server – Fail-over Servers
For any OSE in which you use Running Instances of the server software, you may use up to the same number of passive fail-over Running Instances in a separate OSE on any Server in anticipation of a fail-over event.
The following additional requirements apply if you have licensed the software by Physical Core or individual Virtual OSE under the Per Core licensing model:
- If you license based on Physical Cores and the OSE in which you use the passive fail-over Running Instances is on a separate Server, the number of Physical Cores on the separate Server must not exceed the number of Physical Cores on the Licensed Server and the Core Factor for the Physical Processors in that Server must be the same or lower than the Core Factor for the Physical Processors in the Licensed Server.
- If you license by individual Virtual OSE, the number of Hardware Threads used in that separate OSE must not exceed the number of Hardware Threads used in the OSE in which the active Running Instances are used.
In order to utilize this benefit, you must comply with the following terms:
- Maintain Software Assurance coverage on the server licenses and core licenses under which you run your licensed software and for all CALs under which you access your licensed software.
- Your right to run the passive fail-over instances ends when your Software Assurance coverage ends.
Fail-over server rights do not apply in the case of software moved to shared third party servers under License Mobility through Software Assurance.