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

Why Database AI Agents need Layers?

By

Third part in my Ai series with databases. When building AI solutions within the...

Un-Migrating From the Cloud: T-SQL Tuesday #199

By

This month we have a very interesting invitation from Koen Verbeeck. He has hosted...

T-SQL Tuesday #199: Back to the on-prem

By

It’s the second tuesday of the month, which means T-SQL Tuesday time! This month’s...

Read the latest Blogs

Forums

Unable to restrict permission

By LearningDBA

I have 13 restricted views in my EDW DB. 6 of them are created...

Install SQL Scripts via GUI Wizard

By Jörg

Hallo all! My problem is this: I have quite a bunch of TSQL scripts...

Would You Retire Rather Than ...

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Would You Retire Rather Than...

Visit the forum

Question of the Day

Converting Money

Does this run successfully on a SQL Server 2022, US English default installation?

DECLARE @YenAmount MONEY;
SET @YenAmount = ¥1500; 

SELECT @YenAmount AS RawValue;

See possible answers