January 21, 2015 at 12:41 pm
Hello all,
This is the first time I am trying to create a failover cluster without the log shipping in 2012 as i've done it with a static instance with some database.
Is the "AlwaysON" feature the solution when an application creates random and numerous databases within the instance and we need a failover scenario ?. If so is there a really good document for a newbie ?
much appreciated
JR
January 21, 2015 at 1:52 pm
not sure I'm clear on what you're asking, could you explain a little more please, what are you trying to achieve?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 21, 2015 at 1:58 pm
Thanks for the reply...and sorry for the confusion.
I need to propose a 2 server clustering / failover solution with SQL 2012 and it seems that the log shipping feature will not suit us since we have instances where databases will be created at random through an application.
My question is if the ALWAYSON solution is indeed what I should look into given this scenario?
January 21, 2015 at 2:00 pm
johnnyrmtl (1/21/2015)
Thanks for the reply...and sorry for the confusion.I need to propose a 2 server clustering / failover solution with SQL 2012 and it seems that the log shipping feature will not suit us since we have instances where databases will be created at random through an application.
My question is if the ALWAYSON solution is indeed what I should look into given this scenario?
An AlwaysOn availability group will not automatically add new databases to the group as they're created if that's what you're asking
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 21, 2015 at 2:10 pm
That is indeed my dilemma as new databases will be added continuously to the instance 🙁
What would be the best solution ?
January 21, 2015 at 2:13 pm
Given your statement what you are referring to is Always on Fail over Clustering. There is a difference between this and Always on Availability Groups. And yes, Failover Clustering would be a good solution if an application creates random and numerous databases within the instance? Books online is the best place to get started.
January 21, 2015 at 2:16 pm
Indeed as I see it would be the only solution and would there be a good documentation for a newbie?
AlwaysOn Failover Cluster Instances
As part of the SQL Server AlwaysOn offering, AlwaysOn Failover Cluster Instances leverages Windows Server Failover Clustering (WSFC) functionality to provide local high availability through redundancy at the server-instance level—a failover cluster instance (FCI). An FCI is a single instance of SQL Server that is installed across Windows Server Failover Clustering (WSFC) nodes and, possibly, across multiple subnets. On the network, an FCI appears to be an instance of SQL Server running on a single computer, but the FCI provides failover from one WSFC node to another if the current node becomes unavailable.
January 21, 2015 at 2:17 pm
johnnyrmtl (1/21/2015)
That is indeed my dilemma as new databases will be added continuously to the instance 🙁What would be the best solution ?
What is it you're looking to achieve, high availability on all existing and new databases?
If so, as mentioned already, a failover cluster instance of sql server would provide this. If you require multiple copies of existing and new databases an FCI won't provide this
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
January 21, 2015 at 2:22 pm
I am trying to setup HA on all existing and new databases within an instance.
New databases are constantly added and all databases would be available on a secondary node with the least amount of downtime in case of failure on node one.
January 21, 2015 at 2:22 pm
https://msdn.microsoft.com/en-us/library/hh270278.aspx
Again Books online the one I use is titled High Availability Solutions - SQL Server 2012 Books Online. Try to search for that.
January 21, 2015 at 2:44 pm
JeepHound (1/21/2015)
https://msdn.microsoft.com/en-us/library/hh270278.aspxAgain Books online the one I use is titled High Availability Solutions - SQL Server 2012 Books Online. Try to search for that.
Great thx for that 🙂
Would there be a step by step document besides this overview that worked for you and is easy to read ?
January 21, 2015 at 2:49 pm
JeepHound (1/21/2015)
https://msdn.microsoft.com/en-us/library/hh270278.aspxAgain Books online the one I use is titled High Availability Solutions - SQL Server 2012 Books Online. Try to search for that.
I found some articles that may help
http://www.pythian.com/blog/how-to-install-a-clustered-sql-server-2012-instance-step-by-step-part-1/
January 22, 2015 at 4:37 am
January 22, 2015 at 6:43 am
January 24, 2015 at 8:08 pm
I am somewhat confused as the guide for an " AlwaysOn Failover Cluster Instance" mentions the creation of "Availability groups".
If my application is constantly creating new databases, do I need replace this step or skip it ?
This is because I simply want the instance to failover as a whole and whatever databases it contains not only for an Availability group.
Not sure if I misread the installation 🙁
much appreciated if someone can clear this up :unsure:
Viewing 15 posts - 1 through 15 (of 50 total)
You must be logged in to reply to this topic. Login to reply