{"id":2273,"date":"2013-06-27T00:00:00","date_gmt":"2013-06-27T07:00:00","guid":{"rendered":"https:\/\/blogs.technet.microsoft.com\/dataplatforminsider\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/"},"modified":"2024-01-22T22:49:14","modified_gmt":"2024-01-23T06:49:14","slug":"alwayson-in-sql-server-2014-ctp1","status":"publish","type":"post","link":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/","title":{"rendered":"AlwaysOn in SQL Server 2014 CTP1"},"content":{"rendered":"<p><a href=\"http:\/\/www.google.com\/#gs_rn=17&amp;gs_ri=psy-ab&amp;gs_mss=SQL%20Server%202014%20A&amp;suggest=p&amp;pq=sql%20server%202014%20alwayson&amp;cp=11&amp;gs_id=38&amp;xhr=t&amp;q=sql+server+alwayson&amp;es_nrs=true&amp;pf=p&amp;sclient=psy-ab&amp;oq=SQL+Server++AlwaysOn&amp;gs_l=&amp;pbx=1&amp;bav=on.2,or.r_qf.&amp;bvm=bv.48293060,d.cGE&amp;fp=c85d\"><span style=\"font-size: small\">AlwaysOn<\/span><\/a><span style=\"font-size: small\"> encompasses the SQL Server solutions for mission-critical high availability and disaster recovery. Two solutions were included under the AlwaysOn umbrella in SQL Server 2012: <\/span><a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/ff877884.aspx\"><span style=\"font-size: small\">Availability Groups<\/span><\/a><span style=\"font-size: small\"> and <\/span><a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/ms189134.aspx\"><span style=\"font-size: small\">Failover Cluster Instances<\/span><\/a><span style=\"font-size: small\">. Each solution has different characteristics, making them appropriate for different scenarios, and both can be combined in the same deployment.<\/span><\/p>\n<p><span style=\"font-size: small\">In SQL Server 2014, we are enhancing the availability, scalability, and flexibility of these solutions.<\/span><\/p>\n<p><span style=\"font-size: small\">In this blog, we remind you of the AlwaysOn solutions and then describe the enhancements in <\/span><a href=\"http:\/\/technet.microsoft.com\/evalcenter\/dn205290?WT.mc_id=Blog_SQL_TEE_SQL2014\">SQL Server 2014 CTP1<\/a><span style=\"font-size: small\">. In a future blog, we\u2019ll describe the enhancements in CTP2. <\/span><\/p>\n<p><strong><span style=\"font-size: large\">Availability Groups<\/span><\/strong><\/p>\n<p><span style=\"font-size: small\">Availability Groups (AGs), introduced in SQL Server 2012, integrate and extend features from Database Mirroring and Log Shipping. <\/span><\/p>\n<p><span style=\"font-size: small\">AGs provide high availability for a group of databases through redundant replicas hosted by up to 5 SQL Server instances (1 primary, 4 secondaries). Each SQL Server instance has its own copy of the databases (on its local disks), and AGs continuously synchronize transactions from the primary replica to the secondary replicas. Secondaries can be configured as synchronous or asynchronous allowing to trade data safety for performance. Similarly, they can be configured for automatic or manual failover to account for automated and manual processes. Secondary replicas maintain hot database copies (online state) so that failovers take only seconds. <\/span><\/p>\n<p><span style=\"font-size: small\">AGs enable integrated high availability and disaster recovery configurations without the need for shared storage (e.g. SAN). In addition, secondary replicas can be used to offload read workloads and backups from the primary replica. A SQL Server instance can host replicas for multiple AGs, allowing the distribution of primary replicas across different SQL Server instances. AGs provide many other capabilities such as a Listener (virtual network name) for client connectivity, flexible failover policies, automatic page repair, full cross-feature support, compression, and encryption.<\/span><\/p>\n<p><span style=\"font-size: small\">In SQL Server 2014 CTP1, AGs are enhanced with:<\/span><\/p>\n<ul>\n<li><span style=\"font-size: small\">Increased availability of readable secondaries in multi-site environments<\/span><\/li>\n<li><span style=\"font-size: small\">Increased number of secondaries<\/span><\/li>\n<li><span style=\"font-size: small\">Enhanced Diagnostics<\/span><\/li>\n<li><span style=\"font-size: small\">Integration with Windows Azure<\/span><\/li>\n<\/ul>\n<p><b><span style=\"font-size: small\">Increased availability of readable secondaries in multi-site environments<\/span><\/b><\/p>\n<p><span style=\"font-size: small\">Readable secondary replicas now allow read workloads to run without any disruption even in the presence of lasting network failures or loss of quorum on the underlying Windows Server Failover Cluster. <\/span><\/p>\n<p><span style=\"font-size: small\">This is especially desirable in large-scale geo-distributed environments where network disconnections are not that unusual. This is depicted in the picture below, reports running on readable secondaries far from the main data center will continue running despite a network disconnection. Similarly, new reports started during the network disconnection will run. <\/span><\/p>\n<p><b><span style=\"font-size: small\"><a href=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"margin-right: auto;margin-left: auto;float: none;background-image: none\" title=\"clip_image002\" src=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\" alt=\"clip_image002\" width=\"500\" height=\"302\" border=\"0\" \/><\/a><\/span><\/b><b><\/b><\/p>\n<p><span style=\"font-size: small\">Using the AlwaysOn Dashboard or DMVs, you can detect that a secondary replica is disconnected from the primary and determine the last time and transaction LSN that the secondary committed.<\/span><\/p>\n<p><b><span style=\"font-size: small\">Increased number of secondaries<\/span><\/b><\/p>\n<p><span style=\"font-size: small\">Many customers use AGs to satisfy their high availability, disaster recovery, and reporting requirements in a single solution (to configure and manage). The fact that AG log synchronization is many times faster than other technologies (e.g. Replication or Log Shipping) motivates use readable secondaries for reporting. <\/span><\/p>\n<p><span style=\"font-size: small\">Thus, we have increased the maximum number of secondaries from 4 to 8. <\/span><\/p>\n<p><span style=\"font-size: small\">This facilitates the following scenarios:<\/span><\/p>\n<blockquote><p><span style=\"font-size: small\"><i>a) <\/i><i>Distribution of replicas in a geo-distributed environment<\/i><\/span><\/p>\n<p><span style=\"font-size: small\">Additional replicas can be deployed across the geo-distributed environment, allowing read workloads to run against a local replica.<\/span><\/p>\n<p><span style=\"font-size: small\"><i>b) <\/i><i>Scaling-out of read workloads<\/i><\/span><\/p>\n<p><span style=\"font-size: small\">Additional replicas can be used to load balance read workloads. <\/span><\/p>\n<p><span style=\"font-size: small\">Load balancing can be implemented using simple DNS round-robin or specialized (hardware or software) load balancing solutions.<\/span><\/p><\/blockquote>\n<p><span style=\"font-size: small\">The picture below depicts the increased number of replicas in Object Explorer and the AlwaysOn Dashboard.<\/span><\/p>\n<p><a href=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/4540.AlwaysOn-Dashboard_thumb_1072BC41.png\"><img loading=\"lazy\" decoding=\"async\" style=\"margin-right: auto;margin-left: auto;float: none;background-image: none\" title=\"AlwaysOn Dashboard\" src=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/4540.AlwaysOn-Dashboard_thumb_1072BC41.png\" alt=\"AlwaysOn Dashboard\" width=\"532\" height=\"286\" border=\"0\" \/><\/a><\/p>\n<p><b><span style=\"font-size: small\">Enhanced Diagnostics<\/span><\/b><\/p>\n<p><span style=\"font-size: small\">We have enhanced the diagnostics information for troubleshooting issues. <\/span><\/p>\n<p><span style=\"font-size: small\">This involves:<\/span><\/p>\n<ol>\n<li><span style=\"font-size: small\">Simplifying error messages. For example, separating the generic error <i>\u201creplica can\u2019t become primary<\/i>\u201d into multiple messages, each with a specific cause: <i>\u201cbecause replica is not synchronized\u201d, \u201cbecause windows cluster was started in forced quorum mode\u201d, <\/i>etc<\/span><\/li>\n<li><span style=\"font-size: small\">Making information easier to find and correlate. For example, adding names (AG, replica, and database) to all AlwaysOn XEvents or making additional columns more discoverable in the AlwaysOn Dashboard.<\/span><\/li>\n<\/ol>\n<p><span style=\"font-size: small\">There are many more coming in CTP2. For example, allowing to view XEvents in UTC time, triggering XEvents when replicas change synchronization state, and recording the last time and transaction LSN committed when a replica goes to resolving state.<\/span><\/p>\n<p><b><span style=\"font-size: small\">Integration with Windows Azure Infrastructure Services<\/span><\/b><\/p>\n<p><span style=\"font-size: small\">This year we started supporting <\/span><a href=\"http:\/\/msdn.microsoft.com\/en-us\/library\/jj870962.aspx\"><span style=\"font-size: small\">AGs on Windows Azure<\/span><\/a><span style=\"font-size: small\"> Infrastructure Services (SQL Server running on virtual machines). We support SQL Server 2012 and now SQL Server 2014.<\/span><\/p>\n<p><span style=\"font-size: small\">This enables two scenarios:<\/span><\/p>\n<blockquote><p><span style=\"font-size: small\"><i>a) <\/i><i>High Availability for SQL Server databases hosted in Windows Azure<\/i><\/span><\/p>\n<p><span style=\"font-size: small\">Configure a synchronous secondary replica for automatic failover in case of failure (SQL Server or VM), guest patching (SQL Server or OS), or Windows Azure\u2019s host upgrade.<\/span><\/p>\n<p><span style=\"font-size: small\"><i>b) <\/i><i>Disaster Recovery for on-premise SQL Server databases using Windows Azure<\/i><\/span><\/p>\n<p><span style=\"font-size: small\">Configure one or more asynchronous secondary replicas for your on-premise databases. This allows manually failing over to an Azure replica in case of a failure impacting the on-premise environment. The Azure replicas can be used to offload read workloads and maintain additional backups.<\/span><\/p><\/blockquote>\n<p><span style=\"font-size: small\">The picture below depicts the canonical scenario. The AG has 2 replicas on-premise for high availability and a 3<sup>rd<\/sup> replica on Windows Azure for disaster recovery. <\/span><\/p>\n<p><span style=\"font-size: small\"><a href=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/8640.clip_image006_thumb_4E02AABB.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"margin-right: auto;margin-left: auto;float: none;background-image: none\" title=\"clip_image006\" src=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/8640.clip_image006_thumb_4E02AABB.jpg\" alt=\"clip_image006\" width=\"495\" height=\"260\" border=\"0\" \/><\/a><\/span><\/p>\n<p><span style=\"font-size: small\">Implementing this scenario requires <\/span><a href=\"https:\/\/www.windowsazure.com\/en-us\/manage\/services\/networking\/cross-premises-connectivity\/\"><span style=\"font-size: small\">configuring a site-to-site VPN tunnel<\/span><\/a><span style=\"font-size: small\"> between your on-premise network and Windows Azure. You can use either a physical VPN device or Windows Server 2012 Routing and Remote Access Service (RRAS).<\/span><\/p>\n<p><span style=\"font-size: small\">In CTP2, we\u2019ll release a wizard to greatly simplify adding a replica on Azure.<\/span><\/p>\n<p><strong><span style=\"font-size: large\">Failover Cluster Instances<\/span><\/strong><\/p>\n<p><span style=\"font-size: small\">Failover Cluster Instances (FCIs) enhance the traditional <i>SQL Server Failover Clustering <\/i>feature. FCIs provide high availability for a SQL Server instance through redundant servers that share the same storage (generally a SAN) and appear as a single logical SQL Server instance. Only one active server has access to the storage and can run workloads. When this instance becomes unavailable, the storage ownership moves to a different server where SQL Server is started. SQL Server startup, which includes databases recovery, can take from seconds to a couple of minutes. The secondary servers are passive (can\u2019t run any workloads).<\/span><\/p>\n<p><span style=\"font-size: small\">Given that FCI ensures availability for a full SQL Server instance, it is suited for servers with many instance-level dependencies (e.g. jobs or SSIS packages) or for consolidation, hosting hundreds to thousands of databases. <\/span><\/p>\n<p><span style=\"font-size: small\">In SQL Server 2012, FCIs were enhanced to support multi-subnet clusters, faster and more predictable failover times, flexible failover policies, and tempDB support on local disk.<\/span><\/p>\n<p><span style=\"font-size: small\">In SQL Server 2014 CTP1, FCIs are enhanced with:<\/span><\/p>\n<ul>\n<li><span style=\"font-size: small\">Support for Cluster Shared Volumes <\/span><\/li>\n<li><span style=\"font-size: small\">Enhanced Diagnostics<\/span><\/li>\n<\/ul>\n<p><b><span style=\"font-size: small\">Support for Cluster Shared Volumes <\/span><\/b><\/p>\n<p><span style=\"font-size: small\"><a href=\"http:\/\/technet.microsoft.com\/en-us\/library\/dd759255.aspx\">Cluster Shared Volumes<\/a><\/span><span style=\"font-size: small\"> (CSVs) is a feature of Windows Server Failover Cluster. A CSV is a shared disk that is made accessible to all nodes in a Windows Server Failover Cluster. CSVs build a common global namespace across the cluster (accessible under the %SystemDrive%\\ClusterStorage root directory). This allows creating as many shared volumes as desired in the shared storage, removing the 24 drive letter limitation. For FCI this means that you can create as many FCIs as desired, without having to manage mount points. <\/span><\/p>\n<p><span style=\"font-size: small\">CSVs also increase the resiliency of the cluster by having I\/O fault detection and recovery over alternate communication paths between the nodes in the cluster. This is built on top of the Server Message Block (SMB) protocol. For FCI this means that, if the active server is not able to read\/write directly to the shared storage, the CSV will automatically re-route the request through another node that has access. In addition, if the shared storage has any transient issues, CSV will transparently cache and re-try the operation.<\/span><\/p>\n<p><span style=\"font-size: small\">Finally, CSVs increase the reliability of failovers, as disks don\u2019t need to be unmounted and mounted as with traditional cluster disks. On failover, the new primary SQL Server instance can simply access the CSV.<\/span><\/p>\n<p><span style=\"font-size: small\">CSVs are supported on Windows Server 2012 and Windows Server 2012 R2.<\/span><\/p>\n<p><span style=\"font-size: small\">The picture below depicts two CSVs (Disk 1 and Disk 4) registered in Windows Server Failover Cluster. These CSVs can be selected as the shared disks during the installation of a FCI. <\/span><\/p>\n<p><a href=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/4745.Failover-Cluster-Manager_thumb_78716C89.jpg\"><img loading=\"lazy\" decoding=\"async\" style=\"margin-right: auto;margin-left: auto;float: none;background-image: none\" title=\"Failover Cluster Manager\" src=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/4745.Failover-Cluster-Manager_thumb_78716C89.jpg\" alt=\"Failover Cluster Manager\" width=\"504\" height=\"319\" border=\"0\" \/><\/a><\/p>\n<p><b><span style=\"font-size: small\">Enhanced Diagnostics<\/span><\/b><\/p>\n<p><span style=\"font-size: small\">We made some errors easier to understand. In CTP2, we\u2019ll display information about the underlying Windows Server Failover Cluster in AlwaysOn DMVs.<\/span><\/p>\n<p><span style=\"font-size: small\">Try SQL14 CTP1 and give us feedback! <\/span><a href=\"http:\/\/technet.microsoft.com\/evalcenter\/dn205290?WT.mc_id=Blog_SQL_TEE_SQL2014\">Download it<\/a><span style=\"font-size: small\"> or <\/span><a href=\"http:\/\/www.windowsazure.com\/en-us\/pricing\/trial\/?WT.mc_id=Blog_SQL_TEE_SQL2014\">try it on Windows Azure<\/a><span style=\"font-size: small\">. <\/span><\/p>\n<p><span style=\"font-size: small\">Let us know if you would like to <\/span>join the Technology Adoption Program (TAP)<span style=\"font-size: small\"> and give us your feedback.<\/span><\/p>\n","protected":false},"excerpt":{"rendered":"<p>AlwaysOn encompasses the SQL Server solutions for mission-critical high availability and disaster recovery. Two solutions were included under the AlwaysOn umbrella in SQL Server 2012: Availability Groups and Failover Cluster Instances. Each solution has different characteristics, making them appropriate for different scenarios, and both can be combined in the same deployment.<\/p>\n","protected":false},"author":1457,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"ep_exclude_from_search":false,"_classifai_error":"","_classifai_text_to_speech_error":"","footnotes":""},"post_tag":[],"product":[],"content-type":[2424],"topic":[],"coauthors":[2487],"class_list":["post-2273","post","type-post","status-publish","format-standard","hentry","content-type-best-practices","review-flag-1-1593580431-15","review-flag-2-1593580436-981","review-flag-3-1593580441-293","review-flag-4-1593580446-456","review-flag-5-1593580452-31","review-flag-integ-1593580287-179","review-flag-new-1593580247-437","review-flag-on-pr-1593580815-813","review-flag-vm-1593580806-223"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v27.2 - https:\/\/yoast.com\/product\/yoast-seo-wordpress\/ -->\n<title>AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog\" \/>\n<meta property=\"og:description\" content=\"AlwaysOn encompasses the SQL Server solutions for mission-critical high availability and disaster recovery. Two solutions were included under the AlwaysOn umbrella in SQL Server 2012: Availability Groups and Failover Cluster Instances. Each solution has different characteristics, making them appropriate for different scenarios, and both can be combined in the same deployment.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\" \/>\n<meta property=\"og:site_name\" content=\"Microsoft SQL Server Blog\" \/>\n<meta property=\"article:publisher\" content=\"http:\/\/www.facebook.com\/sqlserver\" \/>\n<meta property=\"article:published_time\" content=\"2013-06-27T07:00:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2024-01-23T06:49:14+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\" \/>\n<meta name=\"author\" content=\"SQL Server Team\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@SQLServer\" \/>\n<meta name=\"twitter:site\" content=\"@SQLServer\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"SQL Server Team\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"6 min read\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\"},\"author\":[{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/author\/sql-server-team\/\",\"@type\":\"Person\",\"@name\":\"SQL Server Team\"}],\"headline\":\"AlwaysOn in SQL Server 2014 CTP1\",\"datePublished\":\"2013-06-27T07:00:00+00:00\",\"dateModified\":\"2024-01-23T06:49:14+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\"},\"wordCount\":1389,\"commentCount\":8,\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\",\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\",\"name\":\"AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog\",\"isPartOf\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\",\"datePublished\":\"2013-06-27T07:00:00+00:00\",\"dateModified\":\"2024-01-23T06:49:14+00:00\",\"breadcrumb\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"AlwaysOn in SQL Server 2014 CTP1\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#website\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/\",\"name\":\"Microsoft SQL Server Blog\",\"description\":\"Official News from Microsoft\u2019s Information Platform\",\"publisher\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization\",\"name\":\"Microsoft SQL Server Blog\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png\",\"contentUrl\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png\",\"width\":259,\"height\":194,\"caption\":\"Microsoft SQL Server Blog\"},\"image\":{\"@id\":\"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"http:\/\/www.facebook.com\/sqlserver\",\"https:\/\/x.com\/SQLServer\",\"https:\/\/www.youtube.com\/user\/MSCloudOS\"]}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/","og_locale":"en_US","og_type":"article","og_title":"AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog","og_description":"AlwaysOn encompasses the SQL Server solutions for mission-critical high availability and disaster recovery. Two solutions were included under the AlwaysOn umbrella in SQL Server 2012: Availability Groups and Failover Cluster Instances. Each solution has different characteristics, making them appropriate for different scenarios, and both can be combined in the same deployment.","og_url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/","og_site_name":"Microsoft SQL Server Blog","article_publisher":"http:\/\/www.facebook.com\/sqlserver","article_published_time":"2013-06-27T07:00:00+00:00","article_modified_time":"2024-01-23T06:49:14+00:00","og_image":[{"url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg","type":"","width":"","height":""}],"author":"SQL Server Team","twitter_card":"summary_large_image","twitter_creator":"@SQLServer","twitter_site":"@SQLServer","twitter_misc":{"Written by":"SQL Server Team","Est. reading time":"6 min read"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#article","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/"},"author":[{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/author\/sql-server-team\/","@type":"Person","@name":"SQL Server Team"}],"headline":"AlwaysOn in SQL Server 2014 CTP1","datePublished":"2013-06-27T07:00:00+00:00","dateModified":"2024-01-23T06:49:14+00:00","mainEntityOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/"},"wordCount":1389,"commentCount":8,"publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg","inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/","url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/","name":"AlwaysOn in SQL Server 2014 CTP1 - Microsoft SQL Server Blog","isPartOf":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage"},"thumbnailUrl":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg","datePublished":"2013-06-27T07:00:00+00:00","dateModified":"2024-01-23T06:49:14+00:00","breadcrumb":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#primaryimage","url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg","contentUrl":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2018\/03\/5657.clip_image002_thumb_5A020A3E.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/2013\/06\/27\/alwayson-in-sql-server-2014-ctp1\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/"},{"@type":"ListItem","position":2,"name":"AlwaysOn in SQL Server 2014 CTP1"}]},{"@type":"WebSite","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#website","url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/","name":"Microsoft SQL Server Blog","description":"Official News from Microsoft\u2019s Information Platform","publisher":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#organization","name":"Microsoft SQL Server Blog","url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png","contentUrl":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-content\/uploads\/2019\/08\/Microsoft-Logo.png","width":259,"height":194,"caption":"Microsoft SQL Server Blog"},"image":{"@id":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/#\/schema\/logo\/image\/"},"sameAs":["http:\/\/www.facebook.com\/sqlserver","https:\/\/x.com\/SQLServer","https:\/\/www.youtube.com\/user\/MSCloudOS"]}]}},"msxcm_display_generated_audio":false,"msxcm_animated_featured_image":null,"_links":{"self":[{"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/posts\/2273","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/users\/1457"}],"replies":[{"embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/comments?post=2273"}],"version-history":[{"count":0,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/posts\/2273\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/media?parent=2273"}],"wp:term":[{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/post_tag?post=2273"},{"taxonomy":"product","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/product?post=2273"},{"taxonomy":"content-type","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/content-type?post=2273"},{"taxonomy":"topic","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/topic?post=2273"},{"taxonomy":"author","embeddable":true,"href":"https:\/\/www.microsoft.com\/en-us\/sql-server\/blog\/wp-json\/wp\/v2\/coauthors?post=2273"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}