Azure SQL automatic index compaction: lower your fill factor under continuous inserts
Does Azure SQL automatic index compaction fix UUIDv7 page density? Yes after a load, but with continuous inserts it needs a fill factor below 100.
Louis Tochon specializes in SQL Server and Oracle database administration, with expertise in performance optimization, scripting, backup/restore, and high availability (Always-On). He is Microsoft Certified Azure Database Administrator Associate. He completed a master's thesis in cybersecurity at SICPA and worked as a SQL Server and Oracle DBA for almost two years at Lombard-Odier. Louis holds a Master's degree in Information Systems from HEC Lausanne. His industry experience covers mainly the banking sector.
Does Azure SQL automatic index compaction fix UUIDv7 page density? Yes after a load, but with continuous inserts it needs a fill factor below 100.
How to check what SQL Server 2025 optimized locking really does with Extended Events: escalations, LAQ attempts and restarts.
sp_invoke_external_rest_endpoint has no limit in SQL Server 2025: each waiting call holds a worker. Compared with Azure SQL.
Translating 4,000 Oracle views, rebuilding indexes offline on Standard Edition, and compressing clustered index to save 1T.
Loading 5 TB from Oracle into SQL Server with SSMA: type overflows, heaps, and the settings that took 788 rows/s to 42,170.
Why SQL Server keeps a full SELECT * serial: I/O cost is never divided across threads. Forcing parallelism burned 3x the CPU.
Column order does not affect equality seeks in SQL Server. Measured on 5M rows, then proven inside the B-tree pages.
UUIDv7 places its timestamp first, but SQL Server compares uniqueidentifier
values starting from the last bytes. Measured on 25,000 inserts: no gain over NEWID().
SSMA fails with ORA-00904 on Oracle SET UNUSED columns. Fix it with a custom select aliasing NULL, no source DDL required.
When the cloud admin is the threat: how SQL Server and MongoDB let you query encrypted data, and what each approach costs.
How SQL Server shifts a whole unique column by +1 without ever creating a duplicate using Split/Sort/Collapse.
How a forgotten transaction exhausted SQL Server’s worker pool, triggered THREADPOOL waits, and only DAC could fix it.