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

Houston AI-Lytics 2026–Powerpoint Slides

By

Thanks to everyone for attending my session on running a Local LLM. If you...

The Book of Redgate: Do the Right Things

By

I do believe that Redgate has been very customer focused since it’s inception. I’ve...

GenAI vs Dashboards: Not the Same (And Never Will Be)

By

There’s a question I’ve been hearing more and more lately, especially as Copilot, Fabric,...

Read the latest Blogs

Forums

T-SQL in SQL Server 2025: JSON_ARRAYAGG

By Steve Jones - SSC Editor

Comments posted to this topic are about the item T-SQL in SQL Server 2025:...

Spring Connections and Learning at PASS On Tour

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Spring Connections and Learning at...

Multiple Sequence Values

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Multiple Sequence Values

Visit the forum

Question of the Day

Multiple Sequence Values

How do I easily get the next 12 sequence values from a sequence object?

See possible answers