Database Administration

External Article

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

Monday Monitor Tips: The MCP Server

By

I have been experimenting with MCP servers in a few ways, and pressing on...

Programmatic Tool Calling with the Claude SDK

By

Programmatic Tool Calling with the Claude SDK Every morning somebody on the team runs the...

A New Word: Mauerbauertraurigkeit

By

mauerbauertraurigkeit – n. inexplicable urge to push people away, even close friends whose company...

Read the latest Blogs

Forums

Removing production permissions when restoring database to non-prod

By webrunner

Hello experts, An application team has asked us to modify a SQL Agent job....

Advanced T-SQL: Replacing Slow Cursors with Window Functions

By sabyda

Comments posted to this topic are about the item Advanced T-SQL: Replacing Slow Cursors...

Finding Bad Queries

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Finding Bad Queries

Visit the forum

Question of the Day

The Service Name

What does @@servicename return?

See possible answers