Performance

SQLServerCentral Article

SQL Window Functions Series: LAG() and LEAD()

  • Article

Dive deep into the powerful SQL window functions, LAG() and LEAD(). Explore their intricacies, discover real-world examples, and avoid common pitfalls.

5 (3)

You rated this post out of 5. Change rating

2023-12-11

8,237 reads

External Article

Optimizing Your Query Plans with the SQL Server 2014 Cardinality Estimator

  • Article

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.

2018-06-26

2,974 reads

Blogs

Secure Your SQL Estate: Best Practices for Azure SQL Security

By

The Castle and the Keys Imagine your Azure SQL environment as a sprawling digital...

The Book of Redgate: Meetings

By

I think we might have forgotten this a bit, but on one of the...

New article: Automating SQL Server Builds

By

I refresh my test SQL Servers at least monthly with a fresh VM. Setting...

Read the latest Blogs

Forums

MySQL 5.6 not writing any logs

By Forum Researcher

We are using MySQL version 5.6 in our Windows Server 2012 R2 environment. We...

How to resolve issue of custom Audit log table containing incorrect data?

By Kevin8

We have created a parent table, child table & Audit log table in SQL...

Change Tracking Default Retention

By Steve Jones - SSC Editor

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

Visit the forum

Question of the Day

Change Tracking Default Retention

I run this command on my SQL Server 2022 database:

ALTER DATABASE AdventureWorks2017 SET CHANGE_TRACKING = ON;
What is the default data retention period?

See possible answers