2024-06-21
452 reads
always on
MSSQL Server AlwaysON: Get alerted for inconsistencies in logins, jobs and databases
This script will create the necessary login and linked servers on a given availability replica. Please ensure that the script is executed on all the replicas.
2022-02-22 (first published: 2022-01-25)
7,781 reads
Configuring Availability Groups in Ubuntu
In this article, we will review how to configure Always On Availability Groups in Ubuntu Server using the Pacemaker cluster. The following are the high-level steps to configure Always On Availability Groups (AOAG) with an Ubuntu server. Install SQL Server on Ubuntu 16.04 Install Pacemaker agents and configure the cluster Create Always On Availability Groups Create […]
2020-08-25
3,575 reads
Deployment of SQL Server 2019 Always On Availability Groups on Azure AKS
Step through a demonstration illustrating a sample deployment of SQL Server 2019 Always On Availability Group cluster on Azure AKS. You'll discover how to leverage the Microsoft Azure-hosted managed Kubernetes service referred to as AKS.
2019-09-10
SQL Server AlwaysOn Availability Groups Monitoring and Alerting - Part 2
In this tip we look at some additional scripts that you can use to monitor your SQL Server AlwaysOn Availability Groups.
2018-12-18
2,855 reads
Configuring SQL Server Always on Azure Servers(Iaas)
Configuration of SQL Server Always on in Azure Virtual machines differs in multiple ways comparing with the on-premise Implementations. This article will help you to have a handy note to configure always on in Azure servers from a DBA perspective.
2020-09-04 (first published: 2018-12-06)
14,448 reads
2018-11-13
700 reads
Automatically Failover (Enable or Disable) Jobs Based on HADR Role
If you have a SQL Server with a High Availability solution (AlwaysOn Availability Groups, Database Mirroring, etc.), and you also have a bunch of jobs which you need to be run on the Primary server only. You need to be able to "failover" the jobs in case the Primary server is no longer Primary.
2018-11-14 (first published: 2018-11-12)
5,879 reads
Always On - Endpoint Ownership
Whoever creates an AlwaysOn group is, by default, the owner of the endpoint. This is generally not a problem…unless that person leaves the company and you need to delete the login.
2018-10-25
15,403 reads
Configure Read Only Routing
The advantage of Setting the readable secondary as Read-Intent Only will allow the secondary server to serve the read-only workload only if the connection string of the application contains Application Intent=Readonly parameter.
2018-02-05
17,338 reads
Blogs
Advice I Like: Art
By Steve Jones
Superheroes and saints never make art. Only imperfect beings can make art because art...
Why Optimize CPU for RDS SQL Server is a game changer
One feature that I have been waiting for years! The new announcement around optimize...
Performance tuning KubeVirt for SQL Server
Following on from my last post about Getting Started With KubeVirt & SQL Server,...
Forums
The AI Bubble and the Weak Foundation Beam
Comments posted to this topic are about the item The AI Bubble and the...
data type gets lost in data flow
Hi, in a simple oledb source->derived column->oledb destination data flow, 2 of my...
i noticed the sqlhealth extende event is on by default , so can i reduce
hi, i noticed the sqlhealth extended event is on by default , and it...
Question of the Day
The Read Committed Snapshot Isolation behaviour
I am currently working with Sql Server 2022 and AdventureWorks database. First of all, let's set the "Read Committed Snapshot" to ON:
use master; go alter database AdventureWorks set read_committed_snapshot on with no_wait; goThen, from Session 1, I execute the following code:
--Session 1 use AdventureWorks; go create table ##t1 (id int, f1 varchar(10)); go insert into ##t1 values (1, 'A');From another session, called Session 2, I open a transaction and execute the following update:
--Session 2 use AdventureWorks; go begin tran; update ##t1 set f1 = 'B' where id = 1;Now, going back to Session 1, what happens if I execute this statement?
--Session 1 select f1 from ##t1 where id = 1;See possible answers