Category : Execution Plans - SentryOne Team Blog

Category: Execution Plans

One way to get an index seek for a leading %wildcard

One way to get an index seek for a leading %wildcard

In an effort to make leading wildcard searches sargable, Aaron Bertrand plays around with a trigram-type implementation in SQL Server.

Rob Farley : Estimated Number of Rows to be Read

Rob Farley : Estimated Number of Rows to be Read

Rob Farley (@rob_farley) uses this month's T-SQL Tuesday to show off the results of one of his Connect items : Estimated Number of Rows to be Read.

Rob Farley : Implementing a Custom Sort

Rob Farley (@rob_farley) discusses some solutions and gotchas for implementing a custom sort using ORDER BY in T-SQL queries.

Paul White : The Sort that Spills to Level 15,000

Paul White shows that SQL Server sometimes produces very misleading information about the impact of sort operations.

Plan Explorer PRO Goes FREE!

SQL Sentry CEO Greg Gonzalez (@SQLsensei) announces the completely free Plan Explorer 3.0, with two groundbreaking new features (Index Analysis and Performance Profiling).

#BackToBasics : DATEFROMPARTS()

Aaron Bertrand (@AaronBertrand) continues his #EntryLevel challenge with July's entry, a treatment of DATEFROMPARTS() and similar functions introduced in SQL Server 2012.

Rob Farley : What's "Actually" going on with that Seek?

Rob Farley (@rob_farley) digs deeper into seeks and actual rows read, demonstrating a case where you want a non-sargable expression in the WHERE clause.

STRING_SPLIT() in SQL Server 2016 : Follow-Up #2

Aaron Bertrand (@AaronBertrand) shows that, at least for a large number of integer parameters, it is actually OPENJSON() that beats both the new STRING_SPLIT() function and TVPs, and leaves traditional splitting methods in the dust.

STRING_SPLIT() in SQL Server 2016 : Follow-Up #1

Aaron Bertrand (@AaronBertrand) follows up on a recent post about the performance of STRING_SPLIT() with a few additional reader-motivated tests.

Performance Surprises and Assumptions : DATEADD()

Aaron Bertrand (@AaronBertrand) explores yet another scenario where a date/time function seems to cause the optimizer to behave unexpectedly.

Bad cardinality estimates from SSMS plans – redux

Aaron Bertrand (@AaronBertrand) shares some insight about early changes to Plan Explorer that help to provide you with the most accurate information we can.