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

Over my years consulting, I've done quite a few performance tests for clients using DiskSpd (formally SQLIO), and I usually manually...