Shulou(Shulou.com)06/03 Report--

After the preparation of the previous three articles, the next step is to complete the implementation of the SQL cluster. Please read on.

SQL Server needs to install .net3.5 components, and Windows Server 2012 and above need to specify the source path when installing operating systems in the graphical interface. Windows Server 2008 and R2 can directly check .net3.5 components for installation.

Open any SQL Server server, insert the SQL installation media and choose the following installation method to install

Then, next, come here to select the desired features:

After selecting the installed feature, fill in a SQL Server network name (highlight: this is also random, but keep in mind that this is the address when all other systems need to fill in SQL FQDN)

It's time to choose the cluster disk (the one with the largest space, of course, the SQL instance is stored on the cluster disk)

Next, fill in the IP address of SQLCluster.

If possible, please specify the SQL service account and password (the high permission of administrator is not required in general production environment, but only one user permission is required)

Enable mixed mode for SQL (based on actual needs) and specify SQL administrator

From the perspective of the data catalog, the SQL instance is indeed stored on the cluster disk

Then the next step is to install.

After the installation is complete, you can see that the disk information has changed when you return to the Windows failover cluster

The first SQL is installed, and then add a second node to the SQL cluster

Open the second SQL server and insert the SQL installation media

Choose to add nodes to the SQL cluster

Next, the next step is useless stuff, you know! Until the cluster node is configured, all the SQL clusters in the current environment will be listed. You just need to select a SQL cluster and add this server as a node. Click next.

In the service account, you need to enter the password again to verify.

After the verification is passed, click next to install.

This completes the implementation of the SQL cluster, but the failover of SQL still needs to be configured manually

Open Windows failover Cluster Administrator, select roles, and select SQL Server right-click properties

Check the preferred owner for two sql servers

On the failover tab, fill in the following information

Explanation: 2 failures are allowed within 3 hours, and after the fault is repaired, the SQL instance is automatically migrated to the master node to run (here, the failure refers to the damage to the operating system of the master node, or unexpected failure such as shutdown due to power outage)

Remember to do the same configuration to DTC!

At this point, the deployment of the entire SQL Server failover cluster is complete, and the addition of more nodes cannot be demonstrated due to limited computer resources. The next article will share with you the experience of SQL Alwayson implementation deployment.

Small summary:

Although it seems that the whole process is made up of four parts, it is easy to review it in detail:

First, make a good plan

Second, divide the storage

Third, deploy and configure Windows failover clusters

Fourth, SQL cluster implementation

Only by summing up more experience, the project will be done in an orderly way!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.