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

Designing a Storage Load Test for SQL Server

By

I’ve been doing storage load tests for SQL Server for a long time, both...

Questions and Answers from Running a Local LLM

By

I had a few random questions from my Running a Local LLM on Your...

Overview of Claude AI Models: Which One to Choose?

By

For those entering the AI space whether professionally or personally I wanted to give...

Read the latest Blogs

Forums

A question about how to store the address in the database

By eichnerm

I have an app that has an address field on the customer and the...

SSIS package failing intermittently on last Excel Component

By Reh23

Good Afternoon, I have a Job which "fires" off an SSIS package (that is...

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:...

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