External Article

Brent Ozar's DBA Training Plan no.15: What’s Your SQL Server Waiting On?

Brent continues his DBA Training Plan: Whenever your queries need to wait on something – storage, locks, memory, whatever – SQL Server tracks what it’s waiting on, and for how long. It’s like you’re seeing INSIDE the server, with all kinds of possible debug points being tracked. All you have to do is ask SQL Server, “What have you been waiting on?”. Here Brent shows you how.

External Article

SQL Change Automation 4.0: Collaborative Database Development Across Visual Studio and SQL Server Management Studio

SQL Change Automation's Development component for developing new databases and modifying existing databases, using migrations, now integrates directly into SQL Server Management Studio as well Visual Studio. It allows teams to collaborate effectively during development, regardless of their preferred IDE, and in a way that integrates easily with common build/integration servers and release management tools.

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

BCA KCP Plaza Sentral Tlpn/wa:085373737551

By balijepalli.p

Jl. Jend. Sudirman No.Kav.47, Karet Semanggi, Kecamatan Setiabudi, Kota Jakarta Selatan, Daerah Khusus Ibukota...

BCA KCP Saharjo Tlpn/Wa:6285188120691

By gQuery

Jl. Dr. Saharjo No.149 G-H, Manggarai Sel., Kec. Tebet, Kota Jakarta Selatan, Daerah Khusus...

BCA KCP Tebet Barat Tlpn/wa:085373737551

By balijepalli.p

Jl. Tebet Barat IX No.40, Tebet Bar., Kec. Tebet, Kota Jakarta Selatan, Daerah Khusus...

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