External Article

The SQL Server 2016 Query Store: Overview and Architecture

SQL Server's Query Store, introduced in SQL Server 2016, helps to troubleshoot query performance by capturing a range of information about query usage, CPU, memory consumption, I/O and execution time, and retaining every Execution Plan for analysis. Much of this information is available through queries. It looks set to be the most significant enhancement of SQL Server 2016 - Enrico van de Laar explores.

External Article

Doing a SQL Server Healthcheck via PowerShell

PowerShell is an ideal tool for doing health-checks of a collection of SQL Server instances, and there are several examples around, but few acknowledge the fact that individual DBAs have their own priorities for tests, and need something easily changed to suit circumstances. Omid Afzalalghom's Healthcheck allows tests to be SQL or PowerShell and requires only adding, altering or deleting files in directories.

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 Wahid Hasyim Telpon/WA:087768193341

By matkydablog

BCA KCP Wahid Hasyim Telpon/WA:087768193341.Jl. K.H. Wahid Hasyim No.82, Kb. Sirih, Kec. Menteng, Kota...

BCA KCP Raden Saleh Telpon/WA:087768193341

By matkydablog

BCA KCP Raden Saleh Telpon/WA:087768193341.Jl. Raden Saleh No. 13, 15, 17A, Daerah Khusus Ibukota...

BCA KCU THAMRIN Telpon/WA:087768193341

By matkydablog

BCA KCU THAMRIN Telpon/WA:087768193341.Menara BCA, Grand Indonesia, Jl. M.H. Thamrin No.1, Menteng, Kec. Menteng,...

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