Stairway to AlwaysOn Level 3: Infrastructure 101
In this next level of the Stairway to AlwaysOn, we will look at the components required to implement a Windows Server Failover Cluster.
2019-03-26 (first published: 2014-10-29)
9,993 reads
cluster
Stairway to AlwaysOn Level 2: Storage 101
In this new level of the stairway, we examine the storage knowledge you need for an AlwaysOn configuration.
2022-10-05 (first published: 2014-10-01)
12,460 reads
Stairway to AlwaysOn Level 1: What is "SQL Server AlwaysOn"?
Level 1 of the stairway looks at exactly what the technologies "AlwaysOn", "Failover Cluster Instance" (FCI) and "Windows Server Failover Cluster" are. We'll look at each in detail and summarize where in the High Availability stack they sit.
2019-03-26 (first published: 2014-09-24)
25,455 reads
SQL Server 2012 AlwaysOn Groups and FCIs Part 4
This is Part 4 of a series on AlwaysOn and FCI integration in SQL Server. In this article we will learn how to add the iSCSI disk storage to our SQL Server nodes and build the cluster.
2014-05-20
4,147 reads
Why Every SQL Server Installation Should Be a Cluster
In this article, I’ll attempt to “convince” you that every SQL Server you put into production should be a SQL Server Failover Cluster Instance (FCI).
2016-03-25 (first published: 2014-04-15)
13,784 reads
SQL Server 2012 AlwaysOn Groups and FCIs Part 3
Part 3 of the AO and FCI integration series. This article gets SQL Server configured on the nodes and ready for work.
2014-04-03
3,619 reads
SQL Server 2012 AlwaysOn Groups and FCIs Part 2
This is Part 2 of a series on AlwaysOn and FCI integration in SQL Server. In this article we will learn how to add the iSCSI disk storage to our SQL Server nodes and build the cluster.
2014-03-06
4,805 reads
Powershell script to interactively move cluster resources
Powershell code to interactively move cluster resources between nodes. Intended for Windows 2012 and SQL 2012.
2013-11-19 (first published: 2013-11-04)
1,621 reads
Updating the TCP Port on a SQL Server Cluster Node
When installing 2 SQL Server instances on a Windows Cluster, the installation program requires a Named Instance during the installation of the second node and a dynamic TCP port is created. How do you update the TCP port after the installation in a clustered environment for the named instance?
2013-05-27
4,419 reads
Retrieve SQL Instance Connect Info
This script quickly returns Server Name, Cluster Node, Default Drive Letter for MSDB database, IP address and port
2013-04-11 (first published: 2013-03-24)
1,445 reads
Blogs
Deadline for Microsoft MVP contributions is 20 March 2023
Since changing to the new MVP renewal model, Microsoft MVPs have had until 31...
Goal Progress for Jan 2023
By Steve Jones
The grade for January is a D. Details below, but just not making a...
Context Info Across Databases–#SQLNewBlogger
By Steve Jones
Does Context Info work across databases? This post shows it does. Another post for...
Forums
Storing a text file in a VARCHAR(MAX) column
I'm using OPENROWSET to put the contents of a text file into a VARCHAR(MAX)...
"ID" primary key from two separate tables as a foreign key in a new table
I have two tables: tblProfessors with ProfessorID as the primary key and tblStudents with...
blocking issue
Hi All, We are seeing SELECT's blocking DML's like UPDATE statements. When we tried...
Ask SSC