External Article

What If You Really DO Need to Shrink a Database?

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.

Blogs

Programmatic Tool Calling with the Claude SDK

By

Programmatic Tool Calling with the Claude SDK Every morning somebody on the team runs the...

A New Word: Mauerbauertraurigkeit

By

mauerbauertraurigkeit – n. inexplicable urge to push people away, even close friends whose company...

Methodology for dealing with bad data in production

By

Pinal Dave wrote up his methodology for what to do when you discover bad...

Read the latest Blogs

Forums

Why SQL Server Database Attach fails and how to repair it

By Nisarg Upadhyay

Comments posted to this topic are about the item Why SQL Server Database Attach...

Fixing P1 Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Fixing P1 Queries

BIT_COUNT() IV

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BIT_COUNT() IV

Visit the forum

Question of the Day

BIT_COUNT() IV

In SQL Server 2025, I run this code:

select bit_count('A')
What is returned?

See possible answers