The Bleeding Edge Versus N Minus One
Risk-averse managers are reticent to upgrade to the latest and greatest. Why is this the case and how can the savvy DBA make the case for and get ready for a newer version of SQL Server?
2016-06-28
2,870 reads
Risk Management
Blogs
A Prompt AI Experiment
By Steve Jones
Prompt AI released recently and I decided to try a few things with the...
SQL Server Is Slow (part 1 of 4)
By Kevin3NF
How should you respond when you get the dreaded Email/Slack/Text/DriveBy from someone yelling at...
Scaling PowerShell – Lessons from a Technical Interview
By gbargsley
Recently, I was in a technical interview where the topic of running PowerShell at...
Forums
how to get notification that my database has corssed 8gb
i have sqlexpress on rds, is there any way i can get notifacation that...
SQL Server, Heaps and Fragmentation
Comments posted to this topic are about the item SQL Server, Heaps and Fragmentation
Stairway to Azure SQL Hyperscale – Level 2: Page Server Architecture Explained
Comments posted to this topic are about the item Stairway to Azure SQL Hyperscale...
Question of the Day
SQL Server, Heaps and Fragmentation
A table without a clustered index (heap) will NOT suffer from fragmentation during frequent updates or deletes. True or False?
See possible answers