How to Create a SQL Cluster – A Summary
This post is a wrapper post for several earlier post I have written. If you follow along the posts, one at a time, you will soon know how to create a SQL Server.
The series of post builds up from a very basic level. However, you should have at least an elementary knowledge of Windows servers and how to work and install software on them.
When you have finished the series, you will know how to create a SQL Server failover cluster to achieve high availability in your environment.
Info. All examples are built on virtual machines in Hyper-V.
Note. This series describes a lab environment, the purpose here is learning. In a real production environment, you must consider more aspects than the once described in these posts. Especially for security.
Index
List of posts to read
- A Brief look at Virtualization and Virtual Machines (Windows 10 Pro)
- Install Windows Server 2016 (Hyper-V)
- Create a LAN between VMs in Hyper-V
- DNS server in local network (Hyper-V)
- DNS names vs. NetBIOS names
- Brief look at Active Directory and Domain Controller
- Shared Storage with iSCSI
- Create a Windows Failover Cluster
- Install SQL Server on a Failover Cluster
General things – good to now
Things that are good to know about that don’t belong to any post in the list above.
No Internet:
The lab environment I created has no internet connection. When Windows Servers with an Evaluation (Trail) License don’t have connection to the Internet for a while they might say that the license has expired, even though they have not! Connect the servers to the Internet (e.g. via default switch in Hyper-V) and restart them, and the trail version should work again.
Disk space:
Make sure you have plenty of disk space. With so many virtual servers installed, they will allocate up a fairly amount of space on your hard drive.
Back to Index.