HA/DR/AG/FCI/Clustering/Business Continuity

SQLServerCentral Article

Set up a Windows Server Fail-over Clusters (As a Precursor to High Availability in Standard Edition)

  • Article

Setting up High Availability in SQL server has some prerequisites. One of these is that the database servers must be members of the same Windows Server Failover Cluster. In this article I show how to succesfully set up WSFC and activate Cluster Aware Updating

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(1)

You rated this post out of 5. Change rating

2024-06-28

11,359 reads

External Article

Add Additional Nodes to SQL Server 2022 and Windows Server 2022 Failover Cluster - Part 3

  • Article

I used the guide in a previous tip on Install SQL Server 2008 on a Windows Server 2008 Cluster Part 1 to install a SQL Server 2008 on a Windows Server 2008 failover cluster (WSFC). Now, I would like to upgrade and migrate my SQL Server 2008 failover clusters to SQL Server 2022 running on Windows Server 2022. What is the process for installation and configuration?

2024-02-26

Blogs

Advice I Like: Overnight Success

By

“Most overnight successes – in fact any significant successes – take at least 5...

T-SQL Tuesday #204: Are tech blogs dead?

By

This is my late response to T-SQL Tuesday #204. I almost always forget about...

Should You Use CHOOSE(): #SQLNewBlogger

By

I was experimenting with CHOOSE() recently after I was asked a question. In a...

Read the latest Blogs

Forums

Why Successful SQL Server Backups Are Not Enough

By Almighty

Comments posted to this topic are about the item Why Successful SQL Server Backups...

Adding Bits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Adding Bits II

An Unlimited Token Budget

By Steve Jones - SSC Editor

Comments posted to this topic are about the item An Unlimited Token Budget

Visit the forum

Question of the Day

Adding Bits II

I have a table, dbo.bittest, where I am testing an application response. This has this structure:

CREATE TABLE [dbo].[BitTest]
(
[insertdate] [datetime] NULL CONSTRAINT [DF__BitTest__insertd__300F11AC] DEFAULT (getdate()),
[a] [bit] NULL
) ON [PRIMARY]
GO
My application runs this code:
INSERT dbo.BitTest
(
    insertdate,
    a
)
VALUES
(DEFAULT, true)
GO

See possible answers