Grant Fritchey

Grant Fritchey is a SQL Server MVP with over 20 years’ experience in IT including time spent in support and development. Grant has worked with SQL Server since version 6.0 back in 1995. He has developed in VB, VB.Net, C# and Java. Grant has authored books for Apress and Simple-Talk, and joined Red Gate as a Product Advocate in January 2011. Find Grant on Twitter @GFritchey or on his blog as the Scary DBA.

External Article

GDPR in the USA

GDPR enforcement began in May of 2018, but if you are doing business in the US, you may not think it applies to you. Grant Fritchey explains why you might be wrong about that and why you need to act now.

2019-04-16

SQLServerCentral Article

It's an Exciting Time

I read a lot of history (as you no doubt notice from my other editorials). I’m currently reading an excellent book on the air war in World War One, Marked for Death: The First War in the Air. One of the fascinating aspects of the war is just how fast the technology shifted. At the […]

You rated this post out of 5. Change rating

2018-01-22

30 reads

SQLServerCentral Article

SQL Server Execution Plans, Second Edition by Grant Fritchey

Every Database Administrator, developer, report writer, and anyone else who writes T-SQL to access SQL Server data, must understand how to read and interpret execution plans. This book leads you right from the basics of capturing plans, through how to interrupt them in their various forms, graphical or XML, and then how to use the information you find there to diagnose the most common causes of poor query performance, and so optimize your SQL queries, and improve your indexing strategy.

3.55 (20)

You rated this post out of 5. Change rating

2017-02-02

18,945 reads

SQLServerCentral Article

The Red Gate Guide to SQL Server Team-based Development

This book shows how to use of mixture of home-grown scripts, native SQL Server tools,
and tools from the Red Gate SQL Toolbelt, to successfully develop database applications in a team environment,
and make database development as similar as possible to "normal" development.

4.67 (3)

You rated this post out of 5. Change rating

2013-08-26

4,743 reads

SQLServerCentral Article

SQL Server Execution Plans

Every day, out in the SQL Server forums, the same questions come up again and again: why is this query running slow? Why isn't my index getting used? In order to arrive at the answer you have to ask the same return question in each case: have you looked at the execution plan? Grant Fritchey provides the only dedicated and detailed book on this essential topic.

2013-03-15

50,744 reads

Blogs

TSQL Tuesday #188 Growing community

By

I am responding late to a T-SQL Tuesday invite from John Sterrett. John’s call...

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

SQL Server 2022 Clusterless Distributed Availability Group

By Pablo Echeverria

Comments posted to this topic are about the item SQL Server 2022 Clusterless Distributed...

Navigating Multi Platform Realities in My Database Life

By dbakevlar

Comments posted to this topic are about the item Navigating Multi Platform Realities in...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers