Stewart Campbell


SQLServerCentral Article

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

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

8,103 reads

SQLServerCentral Article

Basic Always On Availability Groups in SQL Server Standard

Once Windows Server Failover Clusters have been set up, we can set up Availability Groups in SQL Server. This article will focus on setting up Basic Always-On Availability Groups in SQL Server Standard Edition.
This facilitates High Availability in SQL Server Standard, with three levels of availability and failover:
Asynchronous commit with manual or forced failover,
Synchronous commit with manual or forced failover,
Synchronous commit with automatic failover.

(3)

You rated this post out of 5. Change rating

2024-06-05

13,888 reads

Blogs

Cost Visibility: Tracking and Analysing Your Cloud Spend

By

One of the biggest challenges I’ve faced in cloud operations is maintaining clear visibility...

Whiling away an afternoon, thinking

By

I come to Heathrow often. Today is likely somewhere close to 60 trips to...

Black Box vs. Gray Box vs. White Box Testing

By

If your organization is spending money, then meaningful results are a must. Pen testing...

Read the latest Blogs

Forums

Fun with JSON II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fun with JSON II

Changing Data Types

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing Data Types

Answering Questions On Dropped Columns

By Cláudio Silva

Comments posted to this topic are about the item Answering Questions On Dropped Columns

Visit the forum

Question of the Day

Fun with JSON II

I have some data in a table:

CREATE TABLE #test_data
(
    id INT PRIMARY KEY,
    name VARCHAR(100),
    birth_date DATE
);

-- Step 2: Insert rows  
INSERT INTO #test_data
VALUES
(1, 'Olivia', '2025-01-05'),
(2, 'Emma', '2025-03-02'),
(3, 'Liam', '2025-11-15'),
(4, 'Noah', '2025-12-22');
If I run this query, how many rows are returned?
SELECT t1.[key] AS row,
       t2.*
FROM OPENJSON(
     (
         SELECT t.* FROM #test_data AS t FOR JSON PATH
     )
             ) t1
    CROSS APPLY OPENJSON(t1.value) t2;

See possible answers