The parameter sniffing local variable trick copies a parameter into a variable so SQL Server cannot sniff it. This post measures the estimate and the page reads of a sniffed and a local variable procedure, called in both orders. It shows what the trick fixes, and what it leaves slow.
SQL SERVER – Parameter Sniffing Simplest Example
Today we will see a very simple example of the Parameter Sniffing. Let us see a very simple example of the parameter sniffing.
NOCOUNT Performance: What SET NOCOUNT ON Saves in a Loop
NOCOUNT performance depends on the messages that SQL Server no longer sends to the client. This post counts the network packets of a procedure with a 5,000 step loop, with the setting off and on. It also explains why some tests show no time gain, and where the setting helps most.
Procedure Recompilation: Force a New Plan in SQL Server
Procedure recompilation builds a new plan without changing the procedure. A tested demo compares EXEC with WITH RECOMPILE and sp_recompile on a skewed table, with 100,089 reads on a stale plan and 348 on a fresh one. It also shows that sp_recompile removes every cached plan of the procedure.
Application Locks With sp_getapplock: One Job at a Time
Use sp_getapplock to serialize a job, compare transaction and session ownership, handle return codes, and inspect a two-session test.
How to Use GOTO command in SQL Server? – Interview Question of the Week #249
Question: How to Use GOTO command in SQL Server?
Answer: Let us see a simple example of how GOTO works in SQL Server in this blog post.
RETURN Statement in a Stored Procedure: Exit Early
The RETURN statement ends a stored procedure at once and hands back one integer status code. This post builds a small demo, shows how to read the code, stops a procedure after a chosen step, and tests what RETURN does with NULL, text, open transactions and errors.