When Page Prefetching Takes a Back Seat – Exploring Trace Flag 652 in SQL Server
Learn how a trace flag affects SQL Server reading from disk and where this might be a useful thing for you to enable.
2025-09-24
2,392 reads
trace flags
2024-05-13
590 reads
2021-08-30
410 reads
SQL Server 2012 does not come up after service pack upgrade SP4
A failed SQL Server Service Pack upgrade is fixed with a trace flag.
2020-07-27
5,717 reads
2019-12-26
504 reads
Properly Persisted Computed Columns
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
979 reads
Trace Flag 2389 and the new Cardinality Estimator
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
Testing SQL Server Backup Performance with Trace Flag 3042
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,494 reads
Blogs
Finding the Last Last Name in SQL: #SQLNewBlogger
By Steve Jones
I wrote a piece on the new SUBSTRING in SQL Server 2025 and got...
SQL Server 2025 GAs Today
By Steve Jones
If you aren’t watching the Ignite keynotes today, then you might have missed the...
Run SQL Server 2025 and SQL Server Management Studio on macOS Tahoe
Short version You want to get this running as fast as possible. Do these...
Forums
Email change does not work
I changed my email address in Edit Profile page, but it has no effect...
The case for "Understanding our business" training
Comments posted to this topic are about the item The case for "Understanding our...
Specifying the Collation
Comments posted to this topic are about the item Specifying the Collation
Question of the Day
Specifying the Collation
I am dealing with issues on my SQL Server 2022 instance related to collation. I have an instance collation of Latin1_General_CS_AS_KS_WS, but a database collation of Latin1_General_CI_AS. I want to force a few queries to run with a specified collation by using code like this:
DECLARE @c VARCHAR(20) = 'Latin1_General_CI_AS'
SELECT p.PersonType,
p.Title,
p.LastName,
c.CustomerID,
c.AccountNumber
FROM Person.Person AS p
INNER JOIN Sales.Customer AS c
ON c.PersonID = p.BusinessEntityID
COLLATE @c
Will this solve my problem? See possible answers