March 14, 2008 at 5:31 am
I have 2 Windows 2003 r2 servers with a SQL failover cluster installed across the 2 node. Generally I have been running off node1 with node2 as the failover partner. I have purchased the correct licensing for noe1 and from the following I do not need to purchase a license for node2:
Failover clustering is a process where the operating system and SQL Server 2005 work together to provide availability in the event of an application failure, hardware failure, or operating-system error. Failover clustering provides hardware redundancy through a configuration in which critical resources are transferred automatically from a failing machine to an equally configured server to help ensure continuity of service.
When doing failover support, a server is designated as the passive server. The purpose of the passive server is to absorb the data and information held in another server that fails. A passive server does not need a license if the number of processors in the passive server is equal to or less than the number of processors in the active server. The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly
http://www.microsoft.com/sql/howtobuy/activepassive.mspx
My questions are:
1) If I switch my cluster instace to point to node2 for testing node2 in case of a failover, would I need to purchase another licence ? This means I am not doing the repointing because of an 'event of an application failure, hardware failure, or operating-system error' ? Can you please provide information from MS ?
2) How are SQL Licences bound to the windows install in a SQL Server failover cluster configuration ? For instance if node1 legitimately fails due to an 'event of an application failure, hardware failure, or operating-system error' and you failover to node2. Then you think, stuff (forget about) node1 as I have 1 set of licences for SQL Enterprise already and therefore can run with a legitimate licence on node2. Can you please clarify ?
March 14, 2008 at 7:22 am
In the failover concept, the passive failover node (meaning, a node that is used for NOTHING other than being the backup), then you don't need to license it separately. The thought is - the license stays with the "virtual server" being served up by the cluster. You're essentially not licensing a specific node, so much as the cluster.
Now - notice the words "passive failover node". That means that the minute you use that instance/node for anything OTHER than just being the backup "stand-by" hardware, you would then have to license it separately. For example - if you ran a separate group for reporting services, or a second Active/passive install of SQL (so that each node is actively running one of the SQL instances) - then you no longer have a "passive" failover node, so it needs to be licensed.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 14, 2008 at 7:32 am
Hi,
As long as you are only utilizing a single node in an active-passive configuration, you only require 1 license. If you ever decided to change to an active-active configuration, you will need a license for each node. So, in the event you lose the current active node, your license will cover you when node2 takes over as the primary.
Thanks,
Phillip Cox
MCITP - DBAdmin
March 14, 2008 at 9:33 am
but what about the bit when it says:
'The passive server can take the duties of the active server for 30 days. Afterwards, it must be licensed accordingly' ?
In the event of a legitimate failure, node2 would be running off the license purchased. So why are MS restricting the use of it for 30 days ?
March 14, 2008 at 9:45 am
That's actually a good question. Every time I've asked the question to a licensing specialist - I've received essentially the answer Philip mentioned (if your primary server is "dead" for 30 days, then it's not the primary server anymore). I quite honestly am not sure what that 30 day bit means.
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
March 14, 2008 at 9:59 am
One interesting thing is - I can't find that wording anywhere else. The current EULA mentions no 30-day limit, and neither does the How to buy document...
----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
July 21, 2010 at 3:44 pm
What is an active-active configuration in SQL ?
July 22, 2010 at 6:12 am
Active - Active
Is when you create a 2nd instance of sql server and the other node as its primary server.
Node1 is running one sql server instance and Node2 is running the other sql server instance.
This configuration requires 2 sql server licenses. People use this configuration when they want to maximize their hardware. That said you need to capacity plan accordingly. You will need to make sure that a single node has the resources to run both sql server instances in the event of a node failure.
May 25, 2012 at 1:50 am
Here is a link to a 30 day comment. (page 2)
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply