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

Microsoft Fabric Data Agents: Bringing Structured and Unstructured Data Together

By

Most enterprise questions do not live neatly in one place. The numbers may be...

Keeping Redshift System Table History Past 7 Days with S3 Tables

By

Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine...

Updating the Data API Builder

By

I was updating my session for the Data API Builder (DAB) recently, mostly to...

Read the latest Blogs

Forums

Parameter Sensitive Plan Optimization vs. Parameter Sniffing: What SQL Server Fixes and What It Doesn't

By vgupta

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization vs....

Hyperscale Replicas I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Hyperscale Replicas I

The End of Summer

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The End of Summer

Visit the forum

Question of the Day

Hyperscale Replicas I

What types of secondary replicas are available for the Azure SQL Database Hyperscale edition?

See possible answers