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

Catching Up On SQLOrlando

By

Somehow two years have elapsed since my last update; hopefully it won’t be that...

Advice I Like: Pyramid Schemes

By

If someone is trying to convince you it’s not a pyramid scheme, it’s a...

Using Prompt AI for a Travel Data Analysis

By

I was looking back at my year and decided to see if SQL Prompt...

Read the latest Blogs

Forums

Switch partition: NULL boundary id

By vpolasa

I have table: t1 in schema1 with 19 billion records. I have another table...

Minimally Viable Security

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimally Viable Security

Encoding NULL

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Encoding NULL

Visit the forum

Question of the Day

Encoding NULL

What is returned from this code in SQL Server 2025?

SELECT BASE64_ENCODE(NULL)

See possible answers