External Article

Query Store and Parameterization Problems

The query store gives us a novel way of identifying those queries that are causing performance problems when they are parameterized by SQL Server for reuse. Although it is relatively simple to ensure that certain troublesome queries avoid the problem, it is laborious to identify these queries. Additionally, Query Store gives us the means to fix the problem for groups of queries by means of plan guides without changing the DDL at all. Dennes Torres explains the details

External Article

Statistics in SQL: The Kruskal–Wallis Test

Before you report your conclusions about your data, have you checked whether your 'actionable' figures occurred by chance? The Kruskal-Wallis test is a safe way of determining whether samples come from the same population, because it is simple and doesn't rely on a normal distribution in the population. This allows you a measure of confidence that your results are 'significant'. Phil Factor explains how to do it.

Blogs

Installing Old Versions of PowerShell Modules with Their Dependencies

By

I don’t recall where this came up (probably in SQLSlack), but I had a...

In Memory of Andrew Clarke, AKA Phil Factor

By

One of the parts of getting older that really sucks is I seem to...

Leading Through the Noise: Harnessing Data in the Age of Digital Overload

By

The New Leadership Frontier In today’s digital landscape, leaders are no longer just visionaries....

Read the latest Blogs

Forums

taking the rcsi dive

By stan

Hi, we put together an extract that runs every 15 minutes against what i...

Parameter Sensitive Plan Optimization in SQL Server 2022

By Deepam Ghosh

Comments posted to this topic are about the item Parameter Sensitive Plan Optimization in...

Minimum Change Tracking Retention

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Minimum Change Tracking Retention

Visit the forum

Question of the Day

Minimum Change Tracking Retention

If I am running this code:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON (CHANGE_RETENTION=xxx);
What is the minimum amount of time I can set?

See possible answers