在Windows Server 2016和SQL Server Always On可用性组上安装SQL Server 2019

In this article, we will proceed with configuring a SQL Server Always On Availability Groups and perform failover validations.

在本文中,我们将继续配置SQL Server Always On可用性组并执行故障转移验证。

You should go through the following articles and build the infrastructure before proceeding with this article.

在继续本文之前,您应该阅读以下文章并构建基础结构。

  1. A comprehensive guide to SQL Server Always On Availability Groups on Windows Server 2016 Windows Server 2016上SQL Server Always On可用性组的全面指南
    • Configuration of virtual machines on Oracle VirtualBox with Windows Server 2016

      使用Windows Server 2016在Oracle VirtualBox上配置虚拟机
  2. Configure Domain Controller and Active Directory for SQL Server Always On Availability Groups 为SQL Server Always On可用性组配置域控制器和Active Directory
    • It configures the domain controller and active directory features.

      它配置域控制器和活动目录功能。
    • Add the virtual machines to the domain created above.

      将虚拟机添加到上面创建的域中。
  3. Configure failover clusters, storage controllers and quorum configurations for SQL Server Always On Availability Groups 为SQL Server Always On可用性组配置故障转移群集,存储控制器和仲裁配置
    • Windows failover cluster configurations

      Windows故障转移群集配置
    • iSCSI target and initiator configurations

      iSCSI目标和启动器配置
    • File share witness confirmation as Cluster quorum

      文件共享见证人确认为群集仲裁

在Windows Server 2016上为SQL Server Always On可用性组安装SQL Server 2019 (Install SQL Server 2019 on Windows Server 2016 for SQL Server Always On availability groups)

SQL Server 2019 is the latest version available for SQL Server. It has several new features along with the enhancements to existing ones.

SQL Server 2019是可用于SQL Server的最新版本。 它具有几个新功能以及对现有功能的增强。

You can check out SQL Server 2019 articles on SQL Shack to learn more about SQL Server 2019 features.

您可以查看有关SQL Shack的SQL Server 2019文章,以了解有关SQL Server 2019功能的更多信息。

SQL Server 2019 provides developer edition to use for development and test purpose without any license cost.

SQL Server 2019提供开发人员版本以用于开发和测试目的,而无需任何许可证成本。

Open the Microsoft URL and click on download now for developer edition.

打开Microsoft URL ,然后单击立即下载以获取开发人员版本。

Download SQL Server 2019 developer edition

It downloads a setup file. Launch it, and you get the below options.

它下载一个安装文件。 启动它,您将获得以下选项。

  • Basic: It installs SQL Server 2019 with the default configuration of the SQL Server database engine 基本:它将使用SQL Server数据库引擎的默认配置安装SQL Server 2019
  • Custom: In this option, we can select the features, configure them in the installation wizard 自定义:在此选项中,我们可以选择功能,并在安装向导中对其进行配置
  • Download media: It downloads the ISO or CAB file for the SQL Server set up 下载媒体:下载用于SQL Server设置的ISO或CAB文件

Select an installation type

It is a better idea to download the media first and then perform the installation. You can share the media across different servers as well as it avoids issues due to network fluctuations.

最好先下载媒体,然后再执行安装。 您可以在不同服务器之间共享媒体,并且可以避免由于网络波动而引起的问题。

Next, specify the file type, directory and language of the setup.

接下来,指定安装程序的文件类型,目录和语言。

Specify SQL Server installer download

Click on Downloads, and it gives you ISO file, but it might take time depending upon your network bandwidth.

单击下载,它会为您提供ISO文件,但是可能需要一些时间,具体取决于您的网络带宽。

Downloading media

It downloads the SQL Server 2019, as shown below.

它将下载SQL Server 2019,如下所示。

Download successful

在SQLNode1上安装SQL Server 2019 (Install SQL server 2019 on SQLNode1 )

Click on setup.exe, and it opens the SQL Server Installation Center.

单击setup.exe,它将打开SQL Server安装中心。

Install SQL server 2019 on SQLNode1

Navigate to Installation -> New SQL Server standalone installation.

导航到安装->新SQL Server独立安装。

In a SQL Server Always On, we install the SQL as a standalone component on all the nodes. It does not require a SQL Server in a failover cluster mode.

在SQL Server Always On中,我们将SQL作为独立组件安装在所有节点上。 在故障转移群集模式下不需要SQL Server。

New SQL Server standalone installation.

Select the edition of SQL Server 2019. We choose the Developer edition in this demo.

选择SQL Server 2019的版本。在此演示中,我们选择开发人员版本。

Select the edition

Accept the Microsoft software license terms and privacy agreement.

接受Microsoft软件许可条款和隐私协议。

Microsoft software license terms

The next step of Microsoft update is optional. We can ask Microsoft update to check updates for Windows, Microsoft software along with SQL Server 2019. It requires an active internet connection on the server.

下一个 Microsoft更新的步骤是可选的。 我们可以要求Microsoft更新检查Windows,Microsoft软件以及SQL Server 2019的更新。它要求服务器上有活动的Internet连接。

Microsoft update

It installs the required setup files.

它会安装所需的安装文件。

Install setup files

In the next screen, we configure the following options.

在下一个屏幕中,我们配置以下选项。

  • Feature selection: Here, we select the features we want to install in the virtual machine. Select the database engine services from the instance features 功能选择:在这里,我们选择要在虚拟机中安装的功能。 从实例功能中选择数据库引擎服务
  • Instance root directory: Specify a root directory for your SQL Server installation. As per best practice, you should not install it in the root directory where the Windows OS file exists. Similarly, configure the shared feature directory 实例根目录:指定SQL Server安装的根目录。 按照最佳实践,您不应将其安装在Windows OS文件所在的根目录中。 同样,配置共享功能目录

Feature selection

Specify a SQL instance name as a named instance. You can give the SQL instance name to reflect your environment and application.

指定一个SQL实例名称作为命名实例。 您可以指定SQL实例名称以反映您的环境和应用程序。

It creates the instance-specific directory in the specified instance root path.

它在指定的实例根路径中创建特定于实例的目录。

Specify a SQL instance

On the next page, we configure the service account for running the SQL Services. Ideally, you should run the SQL Services with a separate service account in the active directory.

在下一页上,我们配置用于运行SQL Services的服务帐户。 理想情况下,您应该在活动目录中使用单独的服务帐户运行SQL Services。

Let’s hold SQL Server installation at this moment (do not cancel) and connect to the active directory server.

现在让我们保持SQL Server安装(不要取消)并连接到活动目录服务器。

在活动目录中创建服务帐户 (Create a service account in the active directory)

Type dsa.msc in the Windows start -> run and launch the active directory users and computers.

在Windows开始->运行中键入dsa.msc,然后启动活动目录用户和计算机。

Create a service account in the active directory

Right-click on Users folder and create a new user with a unique service account information.

右键单击“用户”文件夹,然后使用唯一的服务帐户信息创建一个新用户。

Service account

As per best practice, you should use the following things in the SQL Server service account.

按照最佳实践,您应该在SQL Server服务帐户中使用以下内容。

  • A complex password (alphanumeric password)

    复杂密码(字母数字密码)
  • Its password should not expire

    其密码不应过期
  • User cannot change the password after the first logon

    首次登录后,用户无法更改密码

Service account details

Once the user is created, add the user to the administrator group on the respective node.

创建用户后,将用户添加到相应节点上的管理员组。

SQL Server 2019安装(续) (SQL Server 2019 installation (Continued) )

Switch back to SQL Server installation on Node 1 and specify the service account for SQL Services. You can also change the default startup mode (automatic or manual) for SQL Services.

切换回节点1上SQL Server安装,并指定SQL Services的服务帐户。 您还可以更改SQL Services的默认启动模式(自动或手动)。

Server Configuration

Now, here comes various default database engine configurations.

现在,这是各种默认的数据库引擎配置。

  • Server Configuration: It gives you the option to choose the authentication mode (Windows or mixed mode). If you select the mixed mode, it enables SQL authentication as well. In this case, specify the password for SA. We can also add AD users as SQL Server administrators. Here, I added the MyDemoSQL\adadmin Windows user as SQL admin. It provides sysadmin permissions to all SQL Server administrators added here

    服务器配置 :它为您提供了选择身份验证模式(Windows或混合模式)的选项。 如果选择混合模式,则还将启用SQL身份验证。 在这种情况下,请指定SA的密码。 我们还可以将AD用户添加为SQL Server管理员。 在这里,我将MyDemoSQL \ adadmin Windows用户添加为SQL admin。 它为此处添加的所有SQL Server管理员提供sysadmin权限。

    Database engine configurations

  • Data Directories: Specify the data root directory, user database, user log and backup directories. You should consider your storage requirements, database growth, IOPS for considering the data directories. For this article, we can go with the default directories

    数据目录 :指定数据根目录,用户数据库,用户日志和备份目录。 您应该考虑存储需求,数据库增长,IOPS,以考虑数据目录。 对于本文,我们可以使用默认目录

    Data Directories

  • TempDB: TempDB is a critical database in SQL Server and responsible for all data sorting, internal objects, row versions, indexes, DBCC checks, temporary objects, order by, group by functions. We should place it on the fastest storage drives such as flash disks

    TempDB :TempDB是SQL Server中的关键数据库,负责所有数据排序,内部对象,行版本,索引,DBCC检查,临时对象,排序依据,按功能分组。 我们应该将其放置在最快的存储驱动器上,例如闪存盘

    According to the Microsoft recommendation, the number of tempdb data files depends upon the number of logical processors

    根据Microsoft的建议,tempdb数据文件的数量取决于逻辑处理器的数量

    Logical processors <= 8: Number of TempDB files should match the logical processors count

    逻辑处理器<= 8 :TempDB文件数应与逻辑处理器数匹配

    Logical processors > 8: Use 8 data files and the increase in multiple of 4 in case of contention

    逻辑处理器> 8 :使用8个数据文件,争用时以4的倍数增加

    SQL Server 2019 set up detects your system configuration, configures the tempdb files accordingly

    SQL Server 2019设置检测到您的系统配置,并相应地配置tempdb文件

    TempDB configuration

  • MAXDOP: It is the maximum degree of Parallelism setting for SQL Server. It controls the number of cores for parallel query execution. This configuration during SQL Server installation is available from SQL Server 2019

    MAXDOP :这是SQL Server的最大并行度设置。 它控制并行查询执行的核心数量。 SQL Server安装过程中的此配置可从SQL Server 2019获得

    MAXDOP

  • Memory: SQL Server is a memory-intensive application. It consumes the whole memory, whatever is assigned to it. By default, SQL Server is designed to use all OS memory. It might cause limited memory for the operating system that eventually leads to high resource utilization and performance issues 内存 :SQL Server是一个占用大量内存的应用程序。 无论分配给它什么,它都会消耗整个内存。 默认情况下,SQL Server设计为使用所有OS内存。 这可能会导致操作系统的内存有限,最终导致高资源利用率和性能问题。

In SQL Server 2019, we get the option to set maximum default memory or the recommended maximum memory. We should assign approx. 70-80% of total server memory to SQL Server in case it does not hold any other application.

在SQL Server 2019中,我们可以选择设置最大默认内存或建议的最大内存。 我们应该分配大约。 如果SQL Server不包含任何其他应用程序,则占SQL Server服务器总内存的70-80%。

For the demo part, we can go with the default configuration.

对于演示部分,我们可以使用默认配置。

Memory

Review your SQL Server 2019 installation configuration and click on Install.

查看您SQL Server 2019安装配置,然后单击``安装''。

Review your SQL Server 2019 configuration

It installs the SQL Server database engine services successfully, as shown below.

它将成功安装SQL Server数据库引擎服务,如下所示。

Setup complete

在SQLNode2上安装SQL Server 2019 (Install SQL server 2019 on SQLNode2)

You can follow the steps mention in the Install SQL server 2019 on the SQLNode1 step and configure SQL Server 2019 on SQLNode as well.

您可以按照在SQLNode1步骤上安装SQL Server 2019中提到的步骤进行操作,也可以在SQLNode上配置SQL Server 2019。

在SQLNode1和SQLNode2上安装SQL Server Management Studio (Install SQL Server Management Studio on SQLNode1 and SQLNode2)

SQL Server Management Studio (SSMS) is not an integral part of the SQL Server set up. It is a separate client application, and Microsoft provides periodic updates (monthly) with bug-fixes and new enhancements.

SQL Server Management Studio(SSMS)不是SQL Server设置的组成部分。 它是一个单独的客户端应用程序,Microsoft定期(每月)提供错误修复和新增强功能的更新。

You can download SSMS latest version from Microsoft Docs and complete the installation wizard on both nodes.

您可以从Microsoft Docs下载最新版本的SSMS,并在两个节点上完成安装向导。

Install SQL Server Management Studio

Launch SSMS and verify the SQL Server 2019 on both the instances.

启动SSMS并在两个实例上验证SQL Server 2019。

Connect to both SQL nodes

在SQLNode1和SQLNode2上启用功能SQL Server Always On可用性组 (Enable feature SQL Server Always On availability groups on SQLNode1 and SQLNode2)

To use the SQL Server Always On, we need to enable the feature on both nodes. Connect to SQLNode1 and open SQL Server 2019 configuration Manager.

若要使用SQL Server Always On,我们需要在两个节点上都启用该功能。 连接到SQLNode1并打开SQL Server 2019配置管理器。

In the configuration manager, navigate to the Always On Availability Groups tab. Here, you can see the Windows failover cluster name. Put a check on the Enable Always On Availability Groups.

在配置管理器中,导航到“始终在线的可用性组”选项卡。 在这里,您可以看到Windows故障转移群集名称。 选中“ 启用始终在线可用性组”。

Enable feature SQL Server always on availability groups on SQLNode1 and SQLNode2

You need to restart the SQL Services. Click OK and restart SQL Services on SQLNode1.

您需要重新启动SQL Services。 单击“确定”,然后在SQLNode1上重新启动SQL Services。

Restart SQL

Similarly, enable the SQL Server Always On availability groups on SQLNode2 and restarts its services.

同样,在SQLNode2上启用SQL Server Always On可用性组并重新启动其服务。

创建一个SQL数据库以添加到可用性组中 (Create a SQL database to add in the availability group)

Connect to SQL Server 2019 on SQLNode1 using SSMS. Expand Always On Availability Groups, and it does not show any groups as of now.

使用SSMS连接到SQLNode1上SQL Server 2019。 展开“永远在线的可用性组”,到目前为止,它不显示任何组。

Create a SQL database

It does not hold any user databases as of now. We need a user database to add in the SQL Server Always On. In the new database configuration window, specify a database name and create it with default configurations.

到目前为止,它不包含任何用户数据库。 我们需要一个用户数据库来添加SQL Server Always On。 在新的数据库配置窗口中,指定数据库名称并使用默认配置创建它。

Database name

As a prerequisite, a full backup should exist for a database to add in the Always On. In the query window of SSMS and run the following command to take full backup in the default directory.

作为先决条件,应该存在完整备份,数据库才能添加到Always On中。 在SSMS的查询窗口中,运行以下命令以在默认目录中进行完整备份。

Backup database sqlshackdemo to disk=’’sqlshackdemo.bak’

配置SQL Server Always On可用性组 (Configure SQL Server Always On availability group)

To create a new availability group, right-click on Always On Availability groups and new availability group wizard.

要创建新的可用性组,请右键单击Always On可用性组和新的可用性组向导。

It launches the new availability group with a brief description of the steps.

它将启动新的可用性组,并简要说明这些步骤。

New availability group

Specify a name for the availability group. Here, I specify the availability group name as SQLAG2019. In the cluster type, it automatically selects the Windows Server Failover Cluster.

指定可用性组的名称。 在这里,我将可用性组名称指定为SQLAG2019。 在群集类型中,它将自动选择Windows Server故障转移群集。

We can skip the options – database level health detection and Per database DTC support for this article.

我们可以跳过这些选项,即本文中的数据库级别运行状况检测和每数据库DTC支持。

Availability group name

In the next step, it shows you the user database and its eligibility to add to the availability group. We have already performed a full database backup, so it shows the status as meets prerequisites. If the database is encrypted, such as SSISDB, we need to specify the password to decrypt the database and configure the AG.

在下一步中,它向您显示用户数据库及其添加到可用性组的资格。 我们已经执行了完整的数据库备份,因此它将状态显示为符合先决条件。 如果数据库是加密的,例如SSISDB,则需要指定密码来解密数据库并配置AG。

Database eligibility for AG

On the next page, we can do the following configurations.

在下一页上,我们可以进行以下配置。

  • Replicas: By default, it shows you the instance you are connected to

    副本 :默认情况下,它向您显示您连接到的实例

    Replicas

    Click on Add replica, specify the SQL instance name for SQLNode2. As we can see here, SQLNode1 takes the primary role, while SQLNode2 takes a secondary role initially.

    单击添加副本,为SQLNode2指定SQL实例名称。 如我们在这里看到的,SQLNode1扮演主要角色,而SQLNode2最初扮演次要角色。

    We can have Synchronous commit and Asynchronous commit for the availability mode. In the synchronization mode, it waits for the acknowledgment from the secondary node before commit records on the primary instance.

    对于可用性模式,我们可以有同步提交和异步提交。 在同步模式下,它会等待来自辅助节点的确认,然后再在主实例上提交记录。

    In an asynchronous mode, it does not wait for any acknowledgment and commit records directly on the primary instance.

    在异步模式下,它不等待任何确认并直接在主实例上提交记录。

    You can refer to this article, Data synchronization in SQL Server Always On Availability Groups for more details on availability modes.

    您可以参考本文SQL Server Always On可用性组中的数据同步,以获取有关可用性模式的更多详细信息。

    Specify replica and sync mode

    We can have automatic failover for the synchronous commit mode; therefore, I choose automatic failover in synchronous mode.

    我们可以为同步提交模式进行自动故障转移。 因此,我选择了同步模式下的自动故障转移。

    Synchronous commit mode

  • Endpoints: It automatically creates the database mirroring endpoints on both the SQL instances on port 5022

    端点 :它会自动在端口5022的两个SQL实例上创建数据库镜像端点

    Endpoints

    备份首选项 (Backup preferences)

    As highlighted earlier, we can use the secondary AG replica for SQL Server backups as well. We will go with the default options in this article. You can refer to the following articles for the backups knowledge in AGs.

    如前所述,我们也可以将辅助AG副本用于SQL Server备份。 我们将在本文中使用默认选项。 您可以参考以下文章,了解AG中的备份知识。

    Backup preferences

    听众 (Listener)

    In SQL Server Always On, we use a listener to connect to the primary node. We might have a primary replica on any of the participating nodes. SQL listener helps to avoid any modification in the connections string, in case of a database failover. They can connect to SQL using listeners, and it always redirects the connection to the primary replica.

    在“ SQL Server始终启用”中,我们使用侦听器连接到节点。 我们可能在任何参与节点上都有一个主副本。 在数据库故障转移的情况下,SQL侦听器有助于避免对连接字符串进行任何修改。 他们可以使用侦听器连接到SQL,并且始终将连接重定向到主副本。

    We can choose to create an availability group listener name or not. If we wish to create a listener, specify a listener’s name and the port.

    我们可以选择是否创建可用性组侦听器名称。 如果我们想创建一个监听器,请指定监听器的名称和端口。

    Listener

    On the next page, select the method for the initial synchronization. You can choose the automatic seeding, full database and log backup, Join only and skip initial data synchronization.

    在下一页上,选择初始同步的方法。 您可以选择自动播种,完整数据库和日志备份,仅连接并跳过初始数据同步。

    Data synchronization

    Next, it performs the validations, and you get success status once it does not report any issues.

    接下来,它执行验证,并且一旦不报告任何问题,您就会获得成功状态。

    Validation

    View Summary

    Review your configuration and click Finish to configure a new availability group and synchronize it. Launch availability group dashboard and you can see the database is in synchronized mode on both SQLNode1 and SQLNode2.

    查看您的配置,然后单击“完成”以配置新的可用性组并对其进行同步。 启动可用性组仪表板,您可以看到SQLNode1和SQLNode2上的数据库处于同步模式。

    Check AG dashboard

    Previously, we do not have any role in the Windows failover clustering. Now, after the AG configuration, we see the role of the SQL listener. Currently, this role is owned by SQLNode1.

    以前,我们在Windows故障转移群集中没有任何作用。 现在,在完成AG配置之后,我们将看到SQL侦听器的角色。 当前,此角色由SQLNode1拥有。

    View role in failover cluster

    为SQL Server Always On可用性组创建SQL侦听器时的常见错误 (A usual error while creating the SQL Listener for SQL Server Always On availability groups)

    You might face the following error while creating the SQL listener.

    创建SQL侦听器时,您可能会遇到以下错误。

    SQL Listener error

    This error comes if the computer account does not have sufficient permissions in the active directory to create the computer objects.

    如果计算机帐户在活动目录中没有足够的权限来创建计算机对象,则会出现此错误。

    To resolve this error, open the active directory and open the Computers Properties and go to Security.

    要解决此错误,请打开活动目录并打开“计算机属性”,然后转到“安全性”。

    Computer properties

    Click on Add and search for the cluster name account in the Computers object type. For example, in my case Windows cluster name is SQLAGCLU.

    单击“添加”,然后在“计算机”对象类型中搜索群集名称帐户。 例如,在我的情况下,Windows群集名称为SQLAGCLU。

    Enter the object name

    Click OK and open the advanced properties. In the advanced properties, click on Add permissions.

    单击确定,然后打开高级属性。 在高级属性中,单击添加权限。

    Assign permissions

    Here, provide the Create Computer objects and Delete Computer objects permissions for the cluster computer account.

    在这里,为群集计算机帐户提供“ 创建计算机”对象和“ 删除计算机”对象权限。

    Create Computer Objects

    After assigning the permissions, it creates the SQL listener successfully.

    分配权限后,它将成功创建SQL侦听器。

    SQL Listener

    We can connect to the primary SQL instance using SQL listener, as shown below.

    我们可以使用SQL侦听器连接到主SQL实例,如下所示。

    Connect primary replica using listener

    SQL Server Always On可用性组的故障转移测试 (Failover testing for SQL Server Always On availability groups)

    Once you have configured the AG replica, it is equally important to test whether the AG failover is working fine or not. You might not come with an accidental surprise later that failover is not working.

    配置完AG副本后,测试AG故障转移是否工作正常同样重要。 以后您可能不会意外地发现故障转移不起作用。

    Right-click on the AG group and click on failover.

    右键单击AG组,然后单击故障转移。

    It shows you the current primary replica, replica status and its failover readiness. Its status should be No data loss to avoid any data loss scenario.

    它向您显示当前的主副本,副本状态及其故障转移准备情况。 其状态应为“ 无数据丢失”,以避免发生任何数据丢失情况。

    Failover testing

    On the next page, connect to the current secondary replica.

    在下一页上,连接到当前的辅助副本。

    Specify replica

    View the summary for the current and new primary replica along with the affected database during failover.

    在故障转移期间,查看当前和新主副本以及受影响数据库的摘要。

    Click on Finish to begin failover

    Click Finish, and it performs a failover from SQLNode1 to SQLNode2 for my demonstration.

    单击“完成”,它将执行从SQLNode1到SQLNode2的故障转移,以进行演示。

    Failover progress

    Refresh the AG console, and you can validate the new primary replica and synchronization status between both nodes.

    刷新AG控制台,您可以验证两个节点之间的新主副本和同步状态。

    View updated dashboard

    In the Failover Cluster Manager also, you have the role owner as SQLNode2.

    同样,在故障转移群集管理器中,角色所有者为SQLNode2。

    Role owner in cluster

    结论 (Conclusion)

    In this series of articles for SQL Server Always On availability groups, we explored end to end process for all configurations including VM, Active Directory, DNS, failover cluster, AG replica. You can follow these articles and prepare your SQL Server Always On availability group for the testing purpose.

    在有关SQL Server Always On可用性组的系列文章中,我们探讨了所有配置(包括VM,Active Directory,DNS,故障转移群集,AG副本)的端到端过程。 您可以按照这些文章并为测试目的准备SQL Server Always On可用性组。

    目录 (Table of contents)

    A comprehensive guide to SQL Server Always On Availability Groups on Windows Server 2016
    Configure Domain Controller and Active Directory for SQL Server Always On Availability Groups
    Configure failover clusters, storage controllers and quorum configurations for SQL Server Always On Availability Groups
    Install SQL Server 2019 on Windows Server 2016 with SQL Server Always On Availability Groups
    Add a new node into existing SQL Server Always On Availability Groups
    Configure Managed Service Accounts for SQL Server Always On Availability Groups
    Windows Server 2016上SQL Server Always On可用性组的全面指南
    为SQL Server Always On可用性组配置域控制器和Active Directory
    为SQL Server Always On可用性组配置故障转移群集,存储控制器和仲裁配置
    在Windows Server 2016和SQL Server Always On可用性组上安装SQL Server 2019
    将新节点添加到现有SQL Server Always On可用性组中
    为SQL Server Always On可用性组配置托管服务帐户

翻译自: https://www.sqlshack.com/install-sql-server-2019-on-windows-server-2016-with-sql-server-always-on-availability-groups/

  • 0
    点赞
  • 0
    评论
  • 0
    收藏
  • 一键三连
    一键三连
  • 扫一扫,分享海报

表情包
插入表情
评论将由博主筛选后显示,对所有人可见 | 还能输入1000个字符
©️2021 CSDN 皮肤主题: 编程工作室 设计师:CSDN官方博客 返回首页
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、C币套餐、付费专栏及课程。

余额充值