Skip to main content

Search This Blog

SQL Server Performance & Troubleshooting – Where Milliseconds Matter 🚀

Unlock hidden SQL Server performance secrets—real benchmarks, execution plan deep dives, and tuning strategies where every millisecond truly matters

Posts

Showing posts with the label Execution Plan

No results found

Powered by Blogger

Theme images by enjoynz

Luca Biondi: SQL Server Performance Expert - Developer at Centro Software s.p.a. - Founder and lead editor of this blog. As a technical author for Stellar and Packt, I specialize in deep-diving into database optimization. My mission? Helping the community master SQL Server, one millisecond at a time.

Choose a topic

If something catches your eye, feel free to explore it — it helps support the blog

Archive

May 202632
April 202630
March 202637
February 20264
January 20261
September 20252
January 20251
April 20232
March 20232
January 20232

Show more Show less

Topics

45 Seconds Series
Accelerated Database Recovery
Accelerated Database Revcovery
ACID
ACID properties of transactions
Adaptive Join
Adaptive Query Processing
ADR
ADR Cleaner Thread Count
AFTER trigger

Show more Show less

The most viewed posts this year

SQL Server, Sub-Queries vs. Cross Apply

February 08, 2020

Hi Guys, Today for you a basic post! We do a comparison between a Query with Sub-Queries and with the Apply operator! So, what are differences between using sub-query and using cross/Outer Apply? Well, if you don't know you should absolutely read this post! Introduction For our comparison we choose these queries: A query with two sub-queries (A subquery is simply a query with another query inside it's select) Select ( Select MAX (OrdRig.Qta1) as conta from OrdRig where Ordrig.idordtes = o.Id and OrdRig.IdComrig is not null), ( Select MAX (OrdRig.Qta2) as conta from OrdRig where Ordrig.idordtes = o.Id and OrdRig.IdComrig is not null) From eco..ordtes o A query that use a Cross Apply operator select t . Qta1 , t . Qta2 from eco .. ordtes o CROSS APPLY ( Select MAX ( OrdRig . Qta1 ) as Qta1 , MAX ( OrdRig . Qta2 ) as Qta2 from OrdRig where Ordrig . ido...

Speaking to Sql Server, sniffing the TDS protocol

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...

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

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...

Total Pageviews

Report Abuse