Scripts

Technical Article

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.

(1)

You rated this post out of 5. Change rating

2018-11-14 (first published: )

6,039 reads

Blogs

Learn about Modern Microsoft Apps in San Diego

By

I wrote about learning today for the editorial: I Can’t Make You Learn. I...

How To Deploy Fabric SQL and Azure SQL Databases with Azure DevOps

By

Fabric has CI/CD built in, but if you've tried to use it for database...

A New Word: Attriage

By

attriage – n. the state of having lost all control over how you feel...

Read the latest Blogs

Forums

Forward Deployed Engineers

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Forward Deployed Engineers

TRY_PARSE vs TRY_CONVERT in SQL Server: From Basics to Practical Usage

By john.martin

Comments posted to this topic are about the item TRY_PARSE vs TRY_CONVERT in SQL...

DBCC CHECKDB Limits II

By Steve Jones - SSC Editor

Comments posted to this topic are about the item DBCC CHECKDB Limits II

Visit the forum

Question of the Day

DBCC CHECKDB Limits II

I have a SQL Server 2025 database that I want to check for corruption every night. One of the things we do is disable indexes used for ETL loads during the weekend and re-enable them on Monday morning. If we run DBCC over the weekend, are our disabled indexes checked for consistency?

See possible answers