2021-08-30
393 reads
2021-08-30
393 reads
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
2020-07-27
5,352 reads
2019-12-26
484 reads
Paul White walks through a new trace flag in SQL Server 2016 designed to yield better execution plans (and performance) for queries involving computed columns.
2017-06-20
4,841 reads
2017-03-10
967 reads
Erin Stellato shows the combined effect of different versions of the cardinality estimator and trace flag 2389 on an ascending key model.
2016-08-23
3,480 reads
Starting with SQL Server 2008 a new feature which allowed us to create compressed backup files by pre-allocating space. This tip will look at the performance impacts of disabling pre-allocation of space using the 3042 SQL Server trace flag.
2015-05-19
6,584 reads
2014-12-04
1,486 reads
The trace flag 8649 is incredibly useful. Alas, the flag is undocumented, unknown, and its full impact difficult to understand. Adam Machanic presents an alternative which you might find useful.
2013-12-23
2,190 reads
2011-09-15
1,940 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...
Testing with AG on Linux with Cluster=NONE. it was all going ok and as...
Hi, I have two tables: one for headers with 9 fields and another for...
We're trying to understand how quick new versions of SQL server can be. Obviously...
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