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

Moving On-Prem PostgreSQL to the Cloud: Picking the Right Path for Big Tables

By

Every PostgreSQL migration eventually hits the same fork in the road. The database is...

A Spread of Vacation

By

I’m off on vacation today. Which is a little weird as I just got...

How AgentDBA Identifies Backup Failures

By

Every DBA has a box like this. Sitting untouched for months. Nobody’s proud of...

Read the latest Blogs

Forums

Calculating Geometric Mean in Power BI

By Dinesh Asanka

Comments posted to this topic are about the item Calculating Geometric Mean in Power...

TempDB Facts I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item TempDB Facts I

Have you done a Mid year check in?

By Pat Wright

Comments posted to this topic are about the item Have you done a Mid...

Visit the forum

Question of the Day

TempDB Facts I

Can I set Accelerated Database Recovery on tempdb?

See possible answers