SQL Window Functions Series: LAG() and LEAD()
Dive deep into the powerful SQL window functions, LAG() and LEAD(). Explore their intricacies, discover real-world examples, and avoid common pitfalls.
2023-12-11
4,551 reads
Dive deep into the powerful SQL window functions, LAG() and LEAD(). Explore their intricacies, discover real-world examples, and avoid common pitfalls.
2023-12-11
4,551 reads
Learn how you can use Windows Performance Monitor and the PAL to gather metrics from your SQL Server instances.
2022-07-20
15,813 reads
It’s not difficult to set up an extended event session, but reviewing and saving the data can be complex. In this article, Edward Pollack demonstrates how to collect extended event data.
2021-11-03
SQL Server perfmon counters provide a wealth of information about performance. In this article, Fabiano Amorim shows how current wisdom about one counter, SQL Compilations/sec, can sometimes be misleading.
2021-08-20
Monitoring SQL Server for performance is a critical part of a DBA’s job. In this article, Edward Pollack explains some of the SQL Server performance monitor data and how to collect it.
2021-07-21
Edward Pollack demonstrates how SQL Server plan cache mining can uncover a wealth of information to help with troubleshooting performance issues.
2021-05-21
In this article, Edward Pollack describes some of the issues when querying against remote data sources. He covers remote SQL Servers and also connecting to a PostgreSQL database.
2020-10-30
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
Developer shops may decide to use Read Committed Snapshot Isolation (RCSI) to reduce contention, and possibly improve performance, but it is not without its own pitfalls. In this article, Uwe Ricken describes a situation where long running transactions caused a severe performance degradation when RCSI was in use.
2018-03-26
3,103 reads
2018-06-05 (first published: 2018-01-11)
2,149 reads
By Steve Jones
I love Chicago. I went to visit three times in 2023: a Redgate event,...
By Brian Kelley
I have found that non-functional requirements (NFRs) can be hard to define for a...
You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...
I have had a hard time to understand how to use EXISTS. I Always...
Dears, We are using Azure Data factory pipes to run some stored procedures against...
Hi, I have SQL Server 2019 installed and when go the Clear Trace database...
Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:
create table t1 (id int primary key, city varchar(50)); insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);If we execute the following query, how will the records be sorted in both environments?
select city from t1 order by city;See possible answers