Born SQL

Forgive me for the title.

The setup My day job involves babysitting a lot of Git repositories hosted on GitHub.

Short version (Edit 2025-11-26: If you still want to use containers, Anthony Nocentino has the answer for you here: https://www.nocentino.com/posts/2025-11-26-sql-server-2025-docker-desktop-avx-issue/) You want to get this running as fast as possible.

The honeymoon is over, and macOS 26 Tahoe broke the Rosetta 2 emulation layer with SQL Server 2025 RC 1 running in a Docker container.

Part of my job at work is to update Transact-SQL reference content.

Yes, SSMS 21 uses the Visual Studio installer.

Three years ago, when the first public preview of SQL Server 2022 (CTP 2.0) was announced, I was a few months in at the SQL Docs team, and had very little to do with that release.

I wrote a stream-of-consciousness post a few months ago about what I do in my day job at Microsoft, working in the Database Docs team.

On behalf of every database administrator everywhere, I implore you not to run CHKDSK on a system that has a live database installed and running.

A discussion on LinkedIn led to this hypothetical “real world” question: Problem statement: I have a SQL Server 2000 database backup that I need to restore to a supported version of SQL Server (preferably SQL Server 2022).

I started working at Microsoft in January 2022.

EDIT: 2024-04-30 I have closed my hosting company, and this site now lives on a Hetzner server in Germany.

A couple of months ago where I work, a major product started undergoing a rebrand.

It’s me again with my apparently semi-annual blog post.

Last year I had a health scare that got my blood pressure at 200-and-something over 100-and-something, soon to be wired up to an IV drip, put through a CT scanner, and a couple of weeks later, poked and prodded from both ends while administered fentanyl.