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

SWAG Saves the Day

By

PASS Summit East is in one week. I was on the road last week...

Upgrading SQL Server Containers on the Laptop

By

I don’t have SQL Server installed on my laptop. In an effort to keep...

How to Find Expensive Queries in Amazon Redshift

By

Slow-running queries can degrade your Redshift cluster’s performance and lead to increased costs. Identifying...

Read the latest Blogs

Forums

BCA KCU PLUIT No. Telp:083831617937

By bbankov

Whatsapp.083831617937 Jl. Pluit Selatan 200 Jakarta Utara, DKI Jakarta, Indonesia 14450  

BCA KCU TANJUNG PRIOK No. Telp:083831617937

By bbankov

Whatsapp.083831617937 Jl. Enggano 22-23 Jakarta Utara, DKI Jakarta, Indonesia 14310

Having Issue deploying a report to an on prem server from PowerBI desktop

By daniel.manke

Using PowerBI Version1.25.9508.3237(January 2026). Installed Microsoft Power BI Desktop (Optimized for Power BI Report...

Visit the forum

Question of the Day

How Long is a Long I/O?

In SQL Server 2025, a long I/O is recorded in the error log with message 833. How long much an I/O request be outstanding before this message is written to the log?

See possible answers