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

A New Word: on tenderhooks

By

on tenderhooks – adj. feeling the primal satisfaction of being needed by someone, which...

Ramblings about data communities and your contributions, no excuses

By

I have been active in the data community throughout my career. I have met...

SQL Server Journey till 2025 (brief)

By

Quick Summary for Microsoft SQL Server till 2025, I am fortunate to be part...

Read the latest Blogs

Forums

how do i map the "current" object entry in for each to one variable

By stan

hi, in an ssis  for each loop over an object variable called MyListVariable, i...

Simulating Mercury’s Orbital Motion Using Pure T-SQL (NASA 2025 Dataset)

By NKTgLaw

SQL Server is typically viewed as a transactional or analytical database engine. However, it...

Azure SQL Database | CREATE EVENT SESSION [Blocking_Capture] ON DATABASE

By DanielP

Hello, Is there a way in Azure SQL Database to change the 'Blocking Process...

Visit the forum

Question of the Day

String Similarity I

On SQL Server 2025, when I run this, what is returned?

SELECT EDIT_DISTANCE_SIMILARITY('SQL Server', 'MySQL')

See possible answers