External Article

Configure SQL Server AlwaysOn Availability Group on a Multi-Subnet Cluster

A “multi-subnet” environment is defined when the OS cluster used as the backbone for AlwaysOn has server nodes that are located in multiple/different subnets. Deploying SQL Server AlwaysOn Availability Groups requires a Windows Server Failover Clustering (WSFC) cluster and each availability replica of a given availability group must reside on a different node of the same WSFC cluster. This post from Manvendra Singh will help you in configuring an HA and DR solution for SQL Server AlwaysOn in multi-subnet networks.

External Article

SQL Server Database Provisioning

Database provisioning for development work isn't always easy. The better that development teams meet business demands for rapid delivery and high quality, the more complex become the requirements for the work of development and testing. More databases are required for testing and development, and they need to be more rapidly kept current. Data and loading needs to match more closely what is in production. Grant Fritchey explains.

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

Read the latest Blogs

Forums

BCA KCU WISMA ASIA Tlpn/wa:085373737551

By thammyvienula

Wisma Asia, Jl. Letjen S. Parman No.Kav. 79, Kota Bambu Sel., Kec. Palmerah, Kota...

BCA KCU THAMRIN. Tlp :085373737845

By Simpson 64488

BCA KCU THAMRIN. Tlp :085373737845.Menara BCA, Grand Indonesia, Jl. M.H. Thamrin No.1, Menteng, Kec....

BCA KCU GREEN GARDEN Tlpn/wa:085373737551

By thammyvienula

Blok A.7 No, Komplek, Jl. Perumahan Green Garden 31-35, RT.1/RW.3, Kedoya Utara, Kec. Kb....

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers