External Article

Yet Another SQL Strategy for Versioned Data

There is a popular design for a database that requires a built-in audit-trail of amendments and additions, where data is never deleted, but superseded by a later version. Whilst this is conceptually simple, it has always made reporting the latest version of data complicated. Alex Kuznetsov joins the debate on the best way of doing this with an example using an indexed view and the filtered index.

Blogs

Narrow Task Decomposition in AI Pipeline Agents

By

A nightly load into sales_fact fails. Ask an orchestrating agent to break down the...

Car Update: August 2026

By

It’s been some time since I provided a car update, so I decided to...

Microsoft Fabric OneLake Shortcuts: When to Use Them and When Not To

By

An architecture scenario Imagine separate Sales, Finance, Shared Data, and Executive Analytics workspaces. Sales...

Read the latest Blogs

Forums

Searching for my own posts

By pietlinden

I have a really stupid question... Is there an easy way to search for...

How to Work with On-Premises AI Models to Generate T-SQL Code

By Daniel Calbimonte

Comments posted to this topic are about the item How to Work with On-Premises...

Escaping Strings

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Escaping Strings

Visit the forum

Question of the Day

Escaping Strings

The STRING_ESCAPE() function requires 2 parameters in SQL Server 2025. The first is a string of text and the second is the type of escape rules being used. What are the options for the second parameter?

See possible answers