Failover clustered licensing - Using 30-day grace period to fix a specific instance or only just for server failure
Tuesday, December 11, 2012 4:46 PM
For this question the architecture is:
I have a windows cluster working with 2 windows servers (2 server in a 1 cluster), running 2 SQL SERVER enterprise instances, and only server #1 is active (both instances should work on server #1).
I know that “In the event of a failover, a 30-day grace period is allowed to restore and run SQL Server.”
So I am sure that if the physical server #1 or the OS in server #1 will fail I got 30 days to fix it.
My question is what will happen if only 1 instance will fail, let’s say, instance #2 will failed to start on Server #1 (bin files problem, registry keys, port configuration, LUNs zoneing, ,etc), and will failover to server #2. In that case I will have Instance #1 on server#1 and instance #2 on server #2.
Is that mean that I need to pay immediatly for Server #2 license, or I can use the 30-day grace period to fix instance #2 on server #1 in that time, and then failover back instance #2 to server #1?
Tuesday, December 11, 2012 5:34 PMModerator
Since the question is a license issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist. You can also visit the following site for more information and support on licensing issues:
Hope this helps.
Wednesday, December 12, 2012 11:23 AM
Although, Microsoft release license guidelines for each & every SQL server version. But there are more complex scenarios for licensing then we think.
Best person to answer your all queries over licensing is MICROSOFT itself.
You can call Microsoft Licensing at 1-800-426-9400, Monday to Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist.
This posting is provided with no warranties and confers no rights.
Please remember to click Mark as Answer and Vote as Helpful on posts that help you. This can be beneficial to other community members reading the thread.