Read from the Right End of the Index: BACKWARD Scans
Optimizing queries is the most fun when you don’t need to add indexes. There’s nothing quite so nice as finding...
Optimizing queries is the most fun when you don’t need to add indexes. There’s nothing quite so nice as finding...
SQLServerCentral has a new place for discussions and Steve Jones hopes you use it. It's a forum built for critiquing and discussion the presentations that the SQL Server community shares with each other.
There still seems to be a lot of fear, uncertainty and doubt, in the community, with regard to use of Hyper-threading (HT) with SQL Server workloads. So, how and when should it be used?
This challenge is to parse and evaluate arithmetic expressions using TSQL.
Here is another example CPU throttling from someone who had a server running with the default “Balanced” Power Plan in...
The BIT data type is an awkward fit for a SQL database. It doesn't have just two values, and it can do unexpected things in expressions. What is worse, it is a flag rather than a predicate, and so its overuse, along with bit masks, is a prime candidate for being listed as a 'SQL Code Smell'. Joe Celko makes the case.
Continuing on with my MCM prep, I was listening to the High Availability/DR prep module today and I was once...
This Friday Steve Jones explores archived data. Can you restate past results or change old data? This week Steve Jones asks how data professionals feel about this and what guidance they give to their customers.
31 Days of SSIS
It’s time to go back to discussing the environment when it comes to SSIS packages. For the...
By Steve Jones
“On the way to a grand goal, celebrate the smallest victories as if each...
Materialized lake views (MLVs) in Microsoft Fabric are an effective way to implement medallion...
Comments posted to this topic are about the item Increase Deadlock Detection
Comments posted to this topic are about the item A Tool is Better than...
Comments posted to this topic are about the item Understanding Deadlock Victim Selection in...
How can I alter the deadlock detection interval to 2 seconds instead of 5 seconds on my SQL Server 2025 instance?
See possible answers