August 5, 2013 at 9:53 am
I have an infrastructure guy that is turned on by the AlwaysOn feature in SQL 2012, I like the idea for DR but not production all the time however I am willing to do the research to see what is the best option. I myself prefer traditional clustering for large databases, SharePoint and document containing DB's in SQL 2012, now we have AlwaysOn and they want to do a 2 node A\P cluster (AlwaysOn) for everything. Would this be the best, most efficient option for a production environment or should traditional clustering be set up with AlwaysOn to the DR site?
MCSE SQL Server 2012\2014\2016
August 5, 2013 at 11:46 am
It's the Database!!! (8/5/2013)
I have an infrastructure guy that is turned on by the AlwaysOn feature in SQL 2012, I like the idea for DR but not production all the time however I am willing to do the research to see what is the best option. I myself prefer traditional clustering for large databases, SharePoint and document containing DB's in SQL 2012, now we have AlwaysOn and they want to do a 2 node A\P cluster (AlwaysOn) for everything. Would this be the best, most efficient option for a production environment or should traditional clustering be set up with AlwaysOn to the DR site?
1) Be sure you dot the eyes and cross the tees when doing FCI clustering AND AlwaysOn for the same system.
2) traditional clustering for SQL Server (FCI now) has an advantage over AGs when you have large BLOBs being thrown around willy-nilly (i.e. SharePoint) because in AG you have to ship the tlog stuff over to the secondary(ies), which can be a LOT of data when big blobs are in play. And the movement/replay of that stuff in single-threaded per database, which combined with network latencies/bandwidth can become a problem in some cases.
3) I note that you can do traditional clustering without Enterprise Edition. You must have EE for AlwaysOn. That isn't a small price difference.
4) The right way to go about this is to determine your NEEDS (HA/DR/scale-out/etc), then review options for solving those needs including costs, complexity, manageability, skill-sets, etc. and do something intelligent based on that matrix.
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
August 5, 2013 at 1:19 pm
thanks Kevin. Sharepoint 2013 does not use BLOB with a tool that we purchased so I can move forward with AG, I have tons of space so I am not worried about the FULL Recov mode. The other document databases does not use BLOB either, so far so good with AlwaysOn instead of FCI. I always in EE unless we do not need it certian features, then it's standard. 😀
MCSE SQL Server 2012\2014\2016
August 5, 2013 at 4:50 pm
It's the Database!!! (8/5/2013)
thanks Kevin. Sharepoint 2013 does not use BLOB with a tool that we purchased so I can move forward with AG, I have tons of space so I am not worried about the FULL Recov mode. The other document databases does not use BLOB either, so far so good with AlwaysOn instead of FCI. I always in EE unless we do not need it certian features, then it's standard. 😀
Must be nice - on ALL of those statements!! 😛
Best,
Kevin G. Boles
SQL Server Consultant
SQL MVP 2007-2012
TheSQLGuru on googles mail service
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply