External Article

Detecting Data Breaches

Data breaches make the news on an almost daily basis. There is no turning back, however, as we are firmly entrenched in this digital way of life. Brian Kelley discusses some of the reasons data breaches occur and what we can do to prevent them.

External Article

Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator

SQL Server 2014 introduces the first major redesign of the SQL Server Query Optimizer cardinality estimation process since version 7.0. The goal for the redesign was to improve accuracy, consistency and supportability of key areas within the cardinality estimation process, ultimately affecting average query execution plan quality and associated workload performance. This paper provides an overview of the primary changes made to the cardinality estimator functionality by the Microsoft query processor team, covering how to enable and disable the new cardinality estimator behavior, and showing how to troubleshoot plan-quality regressions if and when they occur.

Blogs

Programmatically Retrieving MLV Lineage and Refresh Times

By

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

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...

Read the latest Blogs

Forums

BCA KCP Kelapa Gading Raya Tlpn/Wa 0853.7373.7551

By thammyvienula

Jl. Boulevard Raya No.1 Blok L, Klp. Gading Tim., Kec. Klp. Gading, Jkt Utara,...

BCA KCP Mayestik Telpon/WA:08137887595

By tanehome

BCA KCP Mayestik Telpon/WA:08137887595.Jl. Kyai Maja No.77, Gunung, Kec. Kby. Baru, Kota Jakarta Selatan,...

BCA KCP Pluit Samudra Tlpn/Wa 0853.7373.7551

By thammyvienula

Jl. Raya Pluit Utara. 85 Blok E Kav. No. 11, RT.4/RW.5, Pluit, Kecamatan Penjaringan,...

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