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

DiskANN Experiment — Exploring Entry Points and Graph Neighborhoods

By

Introduction I was experimenting with vector search in SQL Server 2025 using approximately 3.8...

T-SQL Tuesday #203: Risk and Reward

By

This is timely, as I’m currently on a boat in the Adriatic taking a...

dataMinds Connect 2026 – Slides & Scripts

By

You can find the slides and SQL scripts for my session “Spice up your...

Read the latest Blogs

Forums

Training the next generation

By Pat Wright

Comments posted to this topic are about the item Training the next generation

Reusing Customer Specific Order Filtering Logic with CROSS APPLY and an Inline TVF (Part 4)

By Imran2629

Comments posted to this topic are about the item Reusing Customer Specific Order Filtering...

PostgreSQL psql Meta Commands: Databases

By Grant Fritchey

Comments posted to this topic are about the item PostgreSQL psql Meta Commands: Databases

Visit the forum

Question of the Day

PostgreSQL psql Meta Commands: Databases

Which of the following meta commands (sometimes called backslash or slash commands) within psql will provide you with information about the databases on the cluster?

See possible answers