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

Overcoming Imposter Syndrome: A Plan

By

My most recent bout with imposter syndrome was with ISACA’s Digital Trust Ecosystem Framework...

Advice I Like: Celebrate Success

By

“On the way to a grand goal, celebrate the smallest victories as if each...

Programmatically Retrieving MLV Lineage and Refresh Times

By

Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...

Read the latest Blogs

Forums

Cara ganti nama tiket Super Air Jet

By joebase

Kesalahan ketik dan ejaan pada tiket Super Air Jet dapat dilakukan melalui Whatsapp 0821-6363-507...

Begini Cara Melakukan Reschedule Tiket Pesawat Batik Air

By mail2robbins

Untuk Melakukan Reschedule [Batik Air] Anda bisa menghubungi CS Batik Air melalui Chat WhatsApp...

BCA KCP Balaraja Tlp.cs 087878229292

By NHATHUOCLP

Wa 087878229292 Jl. Raya Serang Km. 24, Kp. Cariu, RT 003/001, Talagasari, Kec. Balaraja,...

Visit the forum

Question of the Day

Increase Deadlock Detection

How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?

See possible answers