Database Administration

What If You Really DO Need to Shrink a Database?

  • Article

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

Azure Platform Series “You have exceeded the maximum amount of scale changes within the past hour”

By

This blog post relates to where you might be doing scale operations of your...

Bash: “command not found” in IF statement

By

This blog post is about a situation where writing an IF THEN ELSE statement...

The First Data Saturday is Tomorrow

By

Data Saturday #2 – Guatemala is tomorrow. This is the first event on the...

Read the latest Blogs

Forums

Database Architecture

By VastSQL

Hi Experts, Our architecture team come up with a new plan to have multiple...

Calling remote powershell script through SQL server agent

By SQL_Surfer

I have a powershell script in remote server.  When I go to remote server...

Data Privacy Grows in California

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Data Privacy Grows in California

Visit the forum

Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers

Question of the Day

Amend a Commit

See possible answers