External Article

Testing a Flyway Database Migration

Often, we want to test the new version of a database, produced by a Flyway migration, before committing the new migration file, or to test the same migration run on a number of different databases. This article demonstrates how to do it, by generating and using JSON parameter files to run a series of Flyway actions on any number of databases, on any number of servers.

SQLServerCentral Editorial

Knowing When to Respond

I ran into this quote on the Microsoft Learn site, which I thought was a great way to think about how to administer a system: "Without a baseline, every issue encountered could be considered normal and therefore not require any additional intervention." When I've had users file tickets or complain about things not working well, […]

Blogs

ISACA AI Material/Exam Prep Discount (May 18 – June 30, 2026)

By

If you are considering any of the ISACA AI certs like the Advanced Artificial...

A Fabric solution can be very cost effective

By

Are you currently using Microsoft Fabric or considering migrating to it? If so, there...

Track SQL Server Configuration Changes Using the Error Log

By

Track SQL Server Configuration Changes Using the Error Log If you...

Read the latest Blogs

Forums

We Are Eating Our Own Seed Corn

By dbakevlar

Comments posted to this topic are about the item We Are Eating Our Own...

Before Using AI with Business Data, Read This

By rom_c99

Artificial intelligence tools are quickly becoming part of daily business operations, from document analysis...

Designing SQL Server ETL Pipelines That Don't Break at Scale

By SQL Expert

Comments posted to this topic are about the item Designing SQL Server ETL Pipelines...

Visit the forum

Question of the Day

Detecting Deadlocks Quickly

In the Database Engine, when a deadlock is detected, what does the detection interval shrink to (in time)?

See possible answers