Additional Articles


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.

2020-07-29

Blogs

SQL Server 2025 RegEx and AI

By

One of the language changes in SQL Server 2025 that I’ve seen a lot...

T-SQL Tuesday #192: SQL Server 2025 Backup Changes

By

I hosted this month, but I decided to put my own entry in as...

Why Databases Still Fascinate Me

By

I get asked a lot about why or how I began working with databases...

Read the latest Blogs

Forums

How do you approach engineering services consulting?

By furiobellucci

I’ve been thinking a lot about the role of consulting in engineering projects. Having...

Columnstore index question

By Tac11

Hi experts, I’ve been going through several articles and videos about Columnstore indexes, but...

Transactional Replication

By kirk.bay

Recently stood up a 2022 Enterprise server. Have 8 publications with subscriptions on a...

Visit the forum

Question of the Day

Identify a Slipstream Installation

I get a new SQL Server instance from my build team. How can I tell if the instance was installed using a slipstream installation later?

See possible answers