High Availability (HA)

SQLServerCentral Article

Steps for Installing AlwaysOn Availability Groups - SQL 2019

  • Article

With SQL Server 2012 Microsoft introduced the AlwaysOn Availability Group feature, and since then many changes and improvements have been made.  This article is an update to another article, and will cover the prerequisites and steps for installing AlwaysOn in your SQL Server 2019 environment. Prerequisites Before implementing your AlwaysOn Availability Group (AG), make sure […]

You rated this post out of 5. Change rating

2025-12-24 (first published: )

685 reads

External Article

How to Measure Replication Latency in SQL Server AlwaysOn Synchronous Availability Groups

  • Article

Synchronous replicas in SQL Server Availability Groups promise no data loss, but they don’t promise zero delay; under heavy load they can still fall behind. This article shows how to measure and track that hidden replication delay using SQL Server performance counters, so you can see how well your system keeps up during IO‑intensive operations and plan maintenance more safely.

2025-09-17

External Article

PostgreSQL High Availability Options

  • Article

We are deploying a new application that uses PostgreSQL database. My manager has asked me to design high availability into the implementation. As a SQL Server database administrator, I’ve been managing PostgreSQL databases for a while. However, I’m not sure which high availability options to implement. What are the different high availability options for PostgreSQL?

2025-08-27

Contained Availability Groups in SQL Server 2022

  • Article

SQL Server 2022 introduced a new feature called Contained Availability Groups. It allows the Database Administrators to effectively manage the Server Level objects, such as Logins, SQL Agent jobs, etc. in an HA environment. In today's article, we will learn about this new feature of SQL Server. The Challenge of Managing Server Objects in Availability […]

You rated this post out of 5. Change rating

2025-08-20

8,903 reads

SQLServerCentral Article

Basic Always On Availability Groups in SQL Server Standard

  • Article

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

12,705 reads

Blogs

Getting Your Data GenAI-Ready: The Next Stage of Data Maturity

By

I remember a meeting where a client’s CEO leaned in and asked me, “So,...

Learn Better: Pause to Review More

By

If you want to learn better, pause more in your learning to intentionally review.

Azure SQL Managed Instance Next-Gen: Bring on the IOPS

By

If you’ve used Azure SQL Managed Instance General Purpose, you know the drill: to...

Read the latest Blogs

Forums

Azure SQL DBA certification

By ashrukpm

Hello team Can anyone share popular azure SQL DBA certification exam code? and your...

Faster Data Engineering with Python Notebooks: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Faster Data Engineering with Python...

Which Result II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Which Result II

Visit the forum

Question of the Day

Which Result II

I have this code in SQL Server 2022:

CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
    ProductID INT,
    ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
    exec('SELECT ProductName FROM product;')
END;
GO
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned?

See possible answers