SQL Server Performance Weekly Recap – What You Might Have Missed This Week!

SQL Server Performance Weekly Recap – What You Might Have Missed This Week

SQL Server Performance Series – Weekly Roundup

Hi SQL SERVER Guys,

This week on the blog we explored several important SQL Server performance topics.

Some of them are fundamental concepts every SQL Server developer should understand.

Others show real-world tuning scenarios that happen very often in production systems.

If you missed some of the articles, here is a quick recap of the most recent posts published on the blog.

Avoid That Damn Table Spool – A SQL Server Tuning Story

In this article we analyzed a real-world query optimization scenario where a single execution plan operator was responsible for major performance problems.

The culprit? A Table Spool.

We explored why SQL Server sometimes introduces this operator and how a small query rewrite can completely change the execution plan and dramatically improve performance.

👉 Read the full article:

Avoid That Damn Table Spool – SQL Server Performance Tuning Story

The SQL Server Query That Looks Fast… Until It Hits Production

Every SQL Server developer has seen this scenario at least once.

A query runs instantly in development, looks perfect during testing, and everyone thinks the problem is solved.

Then the code reaches production… and suddenly the query becomes extremely slow.

In this article we explain why this happens and how data volume and execution plans can change query behavior dramatically.

👉 Read the full article:

The SQL Server Query That Looks Fast… Until It Hits Production

SQL SERVER! SARGability – The One Concept You Absolutely Must Understand

If there is one concept every SQL Server developer must understand, it is SARGability.

A non-SARGable predicate can silently destroy performance by preventing SQL Server from using indexes efficiently.

In this article we explore how small changes in a query can transform an Index Scan into an Index Seek.

Sometimes a single rewrite can reduce query execution time dramatically.

👉 Read the full article:

SQL SERVER! SARGability – The One Concept You Absolutely Must Understand

The Most Dangerous SQL Server Query Pattern Nobody Talks About

Some SQL Server queries look completely harmless.

They compile successfully, return correct results, and pass code review without any problem.

But under the hood they can force SQL Server to ignore indexes and scan large amounts of data.

In this post we analyze one of the most common hidden performance killers in SQL Server queries.

👉 Read the full article:

The Most Dangerous SQL Server Query Pattern Nobody Talks About

Why Most Developers Should Stop Using XML in SQL Server

XML has been widely used in SQL Server for many years.

However modern workloads often benefit more from lighter data formats like JSON.

In this article we discuss the performance implications of XML storage and why in many cases it is no longer the best option.

👉 Read the full article:

Why Most Developers Should Stop Using XML in SQL Server

The Real Lesson

SQL Server performance tuning is often about understanding small details.

A single function in the wrong place, a non-SARGable predicate, or an unexpected execution plan operator can dramatically impact performance.

The good news is that once you understand these patterns, fixing them is often surprisingly simple.

And remember…

No SQL Server was harmed while writing this weekly recap 😉

See you in the next SQL Server performance deep dive!

Comments

Post a Comment

I Post più popolari

Speaking to Sql Server, sniffing the TDS protocol

Image
Hello friends!  If yesterday you read my post and found it definitely boring (for the topic of course and not for how it was written to the author 😁) well today I promise you that the topic will be much more interesting! Let's talk about Sniffing , let's talk about going to see what happens when we "log in" or when we send a Query to SQL Server.  We will do this by taking a look to the little known tabular data stream (TDS) protocol built on top of the TCP/IP protocol. Ready! The TDS protocol What is the Tabular data stream (TDS) protocol?  The TDS is the protocol used by the SQL Server client Net-Library to communicates with SQL Server . TDS is specific to SQL Server and it is a low-level protocol that specifies both commands and data in a specific arrangement.  TDS encapsulate the TCP/IP protocol. Sniffing TDS packets you can read from the network the requests that your application do to the SQL Server and read the answer .   How to Sniff data from the ne...
Read more

SQL Server, find text in a Trigger, Stored Procedures, View and Function. Two ways and what ways is better

Image
Hi guys, Welcome back! Today a light post about a question that has been asked to me several times. The question is: how to  search for text inside a trigger or a stored procedure ? We have two different ways. A first way using a system view called syscomments: SELECT obj.xtype, text , * FROM sysobjects obj JOIN syscomments com on obj.id = com.id WHERE TEXT like '%text_that_i_am_searching_for%' A second way using a system view called sql_module: SELECT o. name AS Object_Name, o. type_desc , m. definition FROM sys.sql_modules m JOIN sys.objects o ON m. object_id = o. object_id WHERE m. definition Like '%text_that_i_am_searching_for%' ;   Another question is? What differences do we have in using one way instead of the other? Which solution is better? You have to consider that the system view sys.syscomment is obsolete and will be removed sooner or later. So don't use it in production enviroiments. The sys.sql_m...
Read more

SQL Server, Avoid that damn Table Spool!

Image
Hi guys, Welcome back for another post! A light one inspired from what i do during my work: many times I optimize queries rewriting them or adding index and i like it very much! Sometimes you need to use a little imagination, but everything you learn ... sooner or later it will come in handy! Enjoy the reading mates! Avoid the Table Spool, when you can A few days ago I came across a query whose execution time was very high ... or so it was for the client complaining about the problem. Before recreating it, let's create the structures and fill the tables with some data Create table PriceList (Id int identity (1,1) primary Key ,Code Varchar (20)) Insert into PriceList (code) select top 1000 right( '0000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Insert into PriceList (code) select top 4000 right( '1000' + cast ( row_number () over ( order by id) as varchar (4)),4) from artico Create table OrdersList (Id int identity...
Read more