My T-SQL Tuesday #201 invitation. Do temp tables help performance or hurt it? I argue moving data into a #temp table is usually the wrong reflex, and invite you to make your case.

Fabric has CI/CD built in, but if you've tried to use it for database deployments, you've probably already run into its limits. It's still very much in its infancy. The moment you change a column's length, drop a column, or remove a table that already contains data, the deployment fails — Fabric throws up a safety precaution and refuses to proceed. That's a reasonable default, but it stops real schema changes in their tracks. There could be ways around it — third-party tools

Index maintenance has always meant nightly jobs and a window you have to defend. Azure SQL’s new Automatic Index Compaction targets page density directly — so I tested it.