SQL 12 Always On over a WAN with SharePoint
-
Wednesday, October 03, 2012 2:06 PM
I'm working on a SharePoint solution using SQL12. I will have two locations, one in madrid, and one in paris. I have a very fast WAN and high IOPS in both locations. I'm currently thinking of 2 SQL HA pairs, one pair in each location. Performance and BI are key features of this solutions.
The question is, can I extend the Always On feature over a WAN of ~792 miles. I'm hoping that using the Always on, high availability feature and database groups of SQL12 I can deploy my sharepoint across a WAN and maintain a content redundant Sharepoint farm. Essentialy this would be just like setting up multiple servers in a single location, as the same database is fast and available at both locations. If not, I have to use a different architecture and a third party tool for content replication. Can the distance perhaps be mitigated by using sync/async and commit functions?
All Replies
-
Wednesday, October 03, 2012 2:25 PMModerator
You will likely struggle with this due to bandwidth and latency. However, you do realize that AlwaysOn will provide a read only replica (primary replica) of your database on the failover partner? I don't believe Sharepoint will be able to make use of this database as it will need to connect to the virtual network name.
For example you would need a connection string within Sharepoint that would look like this:
Server=tcp:AGListener,1433;Database=AdventureWorks;IntegratedSecurity=SSPI;ApplicationIntent=ReadOnly
I don't think Sharepoint will be able to understand that.
looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
-
Wednesday, October 03, 2012 3:41 PM
Thanks for the quick response. I see your point, and didn't realize the read only replica issue. Can that be mitigated at all? Perhaps through availability group listeners/routing?
In other words if the vname (availability group) were directly routed at each location through its own subnet/IP, could this reconcile the issue, or is it still a connection string problem (notwithstanding any speed issues)? In this manner sharepoint would connect to the vname, I believe. Would that help at all, or would that be the same read only problem?
-
Wednesday, October 03, 2012 5:33 PMModerator
No, this is beyond the design scope of Availability Groups.looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941
- Marked As Answer by kakap Wednesday, October 03, 2012 8:33 PM
-
Tuesday, October 16, 2012 1:29 PM
One follow up - using always on - can I run a full read/write sharepoint install at another location on a fully synchronous copy of the primary - thereby giving me two different locations to read/write to? If so, is the requirement 1gb of bandwith and no more that 10 m/s latency, or something else, or again, this is beyond the design scope?
- Edited by kakap Tuesday, October 16, 2012 1:30 PM
-
Tuesday, October 16, 2012 6:52 PMModeratorNo, only one db/location will be writeable.
looking for a book on SQL Server 2008 Administration? http://www.amazon.com/Microsoft-Server-2008-Management-Administration/dp/067233044X looking for a book on SQL Server 2008 Full-Text Search? http://www.amazon.com/Pro-Full-Text-Search-Server-2008/dp/1430215941

