Database Administration

External Article

What If You Really DO Need to Shrink a Database?

  • Article

You’ve heard that shrinking a database is bad because it introduces both external and internal fragmentation, it causes blocking, it causes transaction log growth while it runs, and it’s slow and single-threaded. You understand that if it’s just a matter of 10-20-30% of a database, and the database is only 100-200GB, you might as well just leave the space there, because you’re gonna end up using it anyway.

2020-07-29

Blogs

Measuring What Matters: Operationalizing Data Trust for CDOs

By

Trust is the currency of the data economy. Without it, even the most advanced...

A Small LLM Fail

By

Another test with Copilot in SSMS (v22 P3) that didn’t go so well. This...

SQL Server Versions: Out With the Old, In With the Supported

By

If your production SQL Servers are still running 2016 (or older) you’re basically banking...

Read the latest Blogs

Forums

Create an HTML Report on the Status of SQL Server Agent Jobs

By Nisarg Upadhyay

Comments posted to this topic are about the item Create an HTML Report on...

SQL Server Ghosts

By Steve Jones - SSC Editor

Comments posted to this topic are about the item SQL Server Ghosts

The Selfish Case for Learning AI

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Selfish Case for Learning...

Visit the forum

Question of the Day

SQL Server Ghosts

For Halloween, what are ghost records?

See possible answers