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

The Book of Redgate: Spread across the world

By

This was Redgate in 2010, spread across the globe. First the EU/US Here’s Asia...

Merry Christmas

By

Today is Christmas and while I do not expect anybody to actual be reading...

Self-Hosting a Photo Server the Whole Family Can Use

By

Until recently, my family's 90,000+ photos have been hidden away in the depths of...

Read the latest Blogs

Forums

SQL Server 2025 Backup Compression Algorithm

By Johan Bijnens

Comments posted to this topic are about the item SQL Server 2025 Backup Compression...

The Large Encoded Value

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Large Encoded Value

The Side Job

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Side Job

Visit the forum

Question of the Day

The Large Encoded Value

I want to use the new BASE64_ENCODE() function in SQL Server 2025, but return a string that isn't large type. What is the longest varbinary string I can pass in and still get a varchar(8000) returned?

See possible answers