{"id":238423,"date":"2021-06-24T16:21:45","date_gmt":"2021-06-24T23:21:45","guid":{"rendered":"https:\/\/virtual-dba.com\/?p=238423"},"modified":"2021-06-24T16:21:47","modified_gmt":"2021-06-24T23:21:47","slug":"migrating-sql-server-alwayson-2017-enterprise-to-2019","status":"publish","type":"post","link":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/","title":{"rendered":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise"},"content":{"rendered":"\n<p>This checklist outlines the steps I took to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition. Having mixed versions of AG&#8217;s is a temporary solution meant for upgrading or migration purposes only and is not intended for long term use.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-preparing-our-new-environment\"><strong>Preparing Our New Environment<\/strong><\/h2>\n\n\n\n<p>1). Stand up new servers, ensure block size of drives used for data\/log files of system &amp; user databases as well as tempdb are sized for 64k. (All drives with ldf\\mdf &amp; TempDB)<\/p>\n\n\n\n<p>2). If this is a multi-subnet environment secondary IP&#8217;s will be needed for each replica being added to an AG Listener. If nodes are all in the same subnet no additional IP&#8217;s required.<br><strong>*** Each IP address assigned to Listener MUST be unique &amp; not used anywhere else on the network<\/strong><\/p>\n\n\n\n<p>3). Install Windows Failover Cluster Manager and .NET Framework 3.5 on each new server.<\/p>\n\n\n\n<p>4). Install\\Configure SQL Server 2019, then restore DB&#8217;s to new instance with &#8216;SA&#8217; as owner.<\/p>\n\n\n\n<p>5). Confirm old &amp; new servers have the same service accounts for SQL Engine\\Agent.<\/p>\n\n\n\n<p>6). Migrate other objects using <strong>DBATools<\/strong> (Logins, Linked Servers, Jobs and disable agent jobs)<br> <strong> URL:<\/strong> <a href=\"https:\/\/dbatools.io\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/dbatools.io\/<\/a><\/p>\n\n\n\n<p>7). Test connectivity for users and applications to minimize &amp; prevent errors later.<\/p>\n\n\n\n<p>8). Enable AlwaysOn High Availability and ADD new servers to the cluster.<\/p>\n\n\n\n<p>9). Run SQL Server Upgrade Advisor on source and resolve any issues reported before migration. CPU impact depends on the environment.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\" id=\"h-synchronizing-new-environment-cutover\"><strong>Synchronizing New Environment &amp; Cutover<\/strong><\/h2>\n\n\n\n<p><strong>*** Take backups in case of Rollback<\/strong><\/p>\n\n\n\n<p>10). ADD new nodes to current AG&#8217;s as Asynchronous secondary replicas temporarily. This can be done by restoring the most recent Full &amp; Diff if backups are configured to run on primary. Confirm AG&#8217;s are still healthy w\\o issues. The DB&#8217;s recently added to the AG will show as Synchronizing\/In Recovery until SQL versions are no longer mixed during the actual cutover process. (screenshot below)<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"401\" height=\"186\" src=\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Not-Synchronizing-Data-Loss.png\" alt=\"Migrating SQL Server - Not Synchronizing Data Loss\" class=\"wp-image-238424\" srcset=\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Not-Synchronizing-Data-Loss.png 401w, https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Not-Synchronizing-Data-Loss-300x139.png 300w\" sizes=\"(max-width: 401px) 100vw, 401px\" \/><\/figure>\n\n\n\n<p>11). Do a manual failover to new primary replica(s). Once failover is successful old replicas will show status of <strong>&#8216;Not Synchronizing(Data Loss)&#8217; <\/strong>(screenshot below)<br> &#8211; Failover from 2017 to 2019 is a one way street and failing back from 2019 to 2017 will not work. If a Rollback is needed then restore most recent 2017 backups.<\/p>\n\n\n\n<figure class=\"wp-block-image size-large\"><img loading=\"lazy\" decoding=\"async\" width=\"642\" height=\"490\" src=\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Synchronizing-In-Recovery.png\" alt=\"Migrating SQL Server Synchronizing In Recovery\" class=\"wp-image-238425\" srcset=\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Synchronizing-In-Recovery.png 642w, https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-Synchronizing-In-Recovery-480x366.png 480w\" sizes=\"(min-width: 0px) and (max-width: 480px) 480px, (min-width: 481px) 642px, 100vw\" \/><figcaption><a href=\"https:\/\/bahtisametcoban.home.blog\/2019\/08\/02\/always-on-availability-group-with-mixed-sql-server-versions\/\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/bahtisametcoban.home.blog\/2019\/08\/02\/always-on-availability-group-with-mixed-sql-server-versions\/<\/a><\/figcaption><\/figure>\n\n\n\n<p>12). Once all is synced verify AG health then test connections for users\\applications. Also manual failover can be tested here as well.<\/p>\n\n\n\n<p>13). Run Full backups on 2019 to start the t-log chain.<\/p>\n\n\n\n<p>14). Once everything is verified as healthy and rollback is not necessary then we can remove the old replica(s) from AG&#8217;s &amp; nodes from the failover cluster.<\/p>\n\n\n\n<p>15). Enable SQL Agent jobs that need to run on new servers. Compare jobs to those on the old nodes.<br>Even though we planned and tested to minimize or eliminate errors with our migration there were still a couple issues that surfaced. This next section includes the issues that we faced post-migration.<\/p>\n\n\n\n<h3 class=\"wp-block-heading\" id=\"h-issues-encountered\">Issues Encountered: <\/h3>\n\n\n<p><b>\u00a0\u00a01). <\/b><span style=\"font-weight: 400;\">Msg 7399, Level 16, State 1, Line 3<\/span><span style=\"font-weight: 400;\"><br \/><\/span><span style=\"font-weight: 400;\">\u00a0 \u00a0 \u00a0 The OLE DB provider for linked server reported an error. The provider reported an <\/span><span style=\"font-weight: 400;\">unexpected catastrophic failure.<\/span><span style=\"font-weight: 400;\"><br \/><\/span><span style=\"font-weight: 400;\"> \u00a0 \u00a0 \u00a0 Msg 7343, Level 16, State 4, Line 3<\/span><span style=\"font-weight: 400;\"><br \/><\/span><span style=\"font-weight: 400;\"> \u00a0 \u00a0 \u00a0 The OLE DB provider for linked server could not UPDATE table . Unknown provider <\/span><span style=\"font-weight: 400;\">error.<\/span><\/p>\n\n\n<h4 class=\"wp-block-heading\" id=\"h-solution\">Solution: <\/h4>\n\n\n\n<p>The ODBC needed to be updated.<\/p>\n\n\n\n<p> 2). Needed to enable xp_cmdshell (may vary per environment)<strong>.<\/strong><\/p>\n\n\n\n<p>I included a few links below for additional reference points. Hopefully this checklist was beneficial and always make sure you test your process to identify and resolve possible issues.<strong><br><br><\/strong><a href=\"https:\/\/docs.microsoft.com\/en-us\/sql\/database-engine\/availability-groups\/windows\/upgrading-always-on-availability-group-replica-instances?view=sql-server-2017\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/docs.microsoft.com\/en-us\/sql\/database-engine\/availability-groups\/windows\/upgrading-always-on-availability-group-replica-instances?view=sql-server-2017<br><br><\/a><a href=\"https:\/\/docs.microsoft.com\/en-us\/sql\/database-engine\/availability-groups\/windows\/distributed-availability-groups?view=sql-server-ver15#sql-server-version-and-edition-requirements-for-distributed-availability-groups\" target=\"_blank\" rel=\"noreferrer noopener\">https:\/\/docs.microsoft.com\/en-us\/sql\/database-engine\/availability-groups\/windows\/distributed-availability-groups?view=sql-server-ver15#sql-server-version-and-edition-requirements-for-distributed-availability-groups<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"<p>This checklist outlines the steps I took to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition. Having mixed versions of AG&#8217;s is a temporary solution meant for upgrading or migration purposes only and is not intended for long term use. Preparing Our New Environment 1). Stand up new servers, ensure block size [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":238426,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_et_pb_use_builder":"off","_et_pb_old_content":"","_et_gb_content_width":"","content-type":"","footnotes":""},"categories":[4166,55],"tags":[1957],"class_list":["post-238423","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-blog","category-sql-server","tag-always-on"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.1 (Yoast SEO v27.1.1) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise<\/title>\n<meta name=\"description\" content=\"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise\" \/>\n<meta property=\"og:description\" content=\"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\" \/>\n<meta property=\"og:site_name\" content=\"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts\" \/>\n<meta property=\"article:published_time\" content=\"2021-06-24T23:21:45+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2021-06-24T23:21:47+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/virtual-dba.com\/media\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"557\" \/>\n\t<meta property=\"og:image:height\" content=\"291\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"XTIVIA\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:site\" content=\"@virtual_dba\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"XTIVIA\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"3 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\"},\"author\":{\"name\":\"XTIVIA\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1\"},\"headline\":\"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise\",\"datePublished\":\"2021-06-24T23:21:45+00:00\",\"dateModified\":\"2021-06-24T23:21:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\"},\"wordCount\":598,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg\",\"keywords\":[\"always on\"],\"articleSection\":[\"Blog\",\"SQL Server\"],\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"CommentAction\",\"name\":\"Comment\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#respond\"]}]},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\",\"url\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\",\"name\":\"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise\",\"isPartOf\":{\"@id\":\"https:\/\/virtual-dba.com\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg\",\"datePublished\":\"2021-06-24T23:21:45+00:00\",\"dateModified\":\"2021-06-24T23:21:47+00:00\",\"description\":\"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.\",\"breadcrumb\":{\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg\",\"width\":557,\"height\":291,\"caption\":\"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/virtual-dba.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/virtual-dba.com\/#website\",\"url\":\"https:\/\/virtual-dba.com\/\",\"name\":\"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts\",\"description\":\"Remote Database Administration\",\"publisher\":{\"@id\":\"https:\/\/virtual-dba.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/virtual-dba.com\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/virtual-dba.com\/#organization\",\"name\":\"Virtual-DBA: Remote DBA | Remote Database Administration\",\"alternateName\":\"Virtual-DBA powered by XTIVIA\",\"url\":\"https:\/\/virtual-dba.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"contentUrl\":\"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg\",\"width\":557,\"height\":291,\"caption\":\"Virtual-DBA: Remote DBA | Remote Database Administration\"},\"image\":{\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/x.com\/virtual_dba\",\"https:\/\/www.linkedin.com\/showcase\/36220649\/\",\"https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg\"],\"description\":\"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.\",\"email\":\"info@xtivia.com\",\"telephone\":\"8886853101\",\"legalName\":\"XTIVIA, Inc\",\"foundingDate\":\"1992-05-01\",\"numberOfEmployees\":{\"@type\":\"QuantitativeValue\",\"minValue\":\"201\",\"maxValue\":\"500\"}},{\"@type\":\"Person\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1\",\"name\":\"XTIVIA\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g\",\"caption\":\"XTIVIA\"},\"url\":\"https:\/\/virtual-dba.com\/author\/xtivia\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise","description":"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.","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:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/","og_locale":"en_US","og_type":"article","og_title":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise","og_description":"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.","og_url":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/","og_site_name":"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts","article_published_time":"2021-06-24T23:21:45+00:00","article_modified_time":"2021-06-24T23:21:47+00:00","og_image":[{"width":557,"height":291,"url":"https:\/\/virtual-dba.com\/media\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg","type":"image\/jpeg"}],"author":"XTIVIA","twitter_card":"summary_large_image","twitter_creator":"@virtual_dba","twitter_site":"@virtual_dba","twitter_misc":{"Written by":"XTIVIA","Est. reading time":"3 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#article","isPartOf":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/"},"author":{"name":"XTIVIA","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1"},"headline":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise","datePublished":"2021-06-24T23:21:45+00:00","dateModified":"2021-06-24T23:21:47+00:00","mainEntityOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/"},"wordCount":598,"commentCount":0,"publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg","keywords":["always on"],"articleSection":["Blog","SQL Server"],"inLanguage":"en-US","potentialAction":[{"@type":"CommentAction","name":"Comment","target":["https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#respond"]}]},{"@type":"WebPage","@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/","url":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/","name":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise","isPartOf":{"@id":"https:\/\/virtual-dba.com\/#website"},"primaryImageOfPage":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage"},"image":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage"},"thumbnailUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg","datePublished":"2021-06-24T23:21:45+00:00","dateModified":"2021-06-24T23:21:47+00:00","description":"This article outlines the steps taken to migrate SQL Server Always On 2017 Enterprise to 2019 Enterprise edition.","breadcrumb":{"@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#primaryimage","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/Migrating-SQL-Server-AlwaysOn-from-2017-Enterprise-to-2019-Enterprise.jpg","width":557,"height":291,"caption":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise"},{"@type":"BreadcrumbList","@id":"https:\/\/virtual-dba.com\/blog\/migrating-sql-server-alwayson-2017-enterprise-to-2019\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/virtual-dba.com\/"},{"@type":"ListItem","position":2,"name":"Migrating SQL Server AlwaysOn from 2017 Enterprise to 2019 Enterprise"}]},{"@type":"WebSite","@id":"https:\/\/virtual-dba.com\/#website","url":"https:\/\/virtual-dba.com\/","name":"Virtual-DBA Remote DBA Services &amp; Support - Certified Database Experts","description":"Remote Database Administration","publisher":{"@id":"https:\/\/virtual-dba.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/virtual-dba.com\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/virtual-dba.com\/#organization","name":"Virtual-DBA: Remote DBA | Remote Database Administration","alternateName":"Virtual-DBA powered by XTIVIA","url":"https:\/\/virtual-dba.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/","url":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","contentUrl":"https:\/\/virtual-dba.com\/wp-content\/uploads\/V-DBA-Database-Services-and-Support-Featured-Logo.jpg","width":557,"height":291,"caption":"Virtual-DBA: Remote DBA | Remote Database Administration"},"image":{"@id":"https:\/\/virtual-dba.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/x.com\/virtual_dba","https:\/\/www.linkedin.com\/showcase\/36220649\/","https:\/\/www.youtube.com\/channel\/UCx3AIeUQ2ziTLKZSJDZ-SEg"],"description":"Eliminate database downtime and spiraling costs with XTIVIA\u2019s Virtual-DBA. In today\u2019s always-on business world, gaps in 24x7 on-call DBA support, neglected maintenance and security, or a stretched team struggling with overwhelming workloads can lead to costly disruptions and threaten business continuity. XTIVIA\u2019s Virtual-DBA provides the immediate, expert database administration you need, exactly when you need it, ensuring optimal performance, ironclad security, and significant cost savings without the burden of expanding your in-house team. The goal of Virtual-DBA is to provide a cost-effective solution for organizations seeking to optimize the security, management, maintenance, availability, and performance of their critical business systems, whether self-managed or cloud-managed (e.g., AWS RDS, Azure SQL Database). We accomplish this through a comprehensive remote DBA service offering designed specifically to meet the Oracle\u00ae, DB2\u00ae, Informix\u00ae, MySQL\u2122, PostgreSQL\u00ae, MongoDB\u00ae, MariaDB, and Microsoft SQL Server\u00ae, CockroachDB, Databricks, AWS, and Azure needs of our clients.","email":"info@xtivia.com","telephone":"8886853101","legalName":"XTIVIA, Inc","foundingDate":"1992-05-01","numberOfEmployees":{"@type":"QuantitativeValue","minValue":"201","maxValue":"500"}},{"@type":"Person","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/2d86f74bed0c3f1b49100f7fdf7d78d1","name":"XTIVIA","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/virtual-dba.com\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0d3648a00e319a37cf8d6d19f762acfbbb4fd0320fd8a6d6b1e64f44a2a6f259?s=96&d=mm&r=g","caption":"XTIVIA"},"url":"https:\/\/virtual-dba.com\/author\/xtivia\/"}]}},"_links":{"self":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/238423","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/comments?post=238423"}],"version-history":[{"count":0,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/posts\/238423\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media\/238426"}],"wp:attachment":[{"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/media?parent=238423"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/categories?post=238423"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/virtual-dba.com\/wp-json\/wp\/v2\/tags?post=238423"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}