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.

Twitter: @https://twitter.com/gfritchey
Website: https://scarydba.com
LinkedIn: https://www.linkedin.com/in/grant-fritchey/
Bluesky: https://bsky.app/profile/gfritchey.bsky.social

All authors

Excel Within Management Studio

by Grant Fritchey

The Scary DBA

Aaron Bertrand has put in a Connect request for a feature whereby data returned as a grid from a query...

2010-01-13

753 reads

SQL Server Standard Volume 7 Issue 1

by Grant Fritchey

The Scary DBA

Kathi Kellenberger’s fantastic new article is available in the latest issue of SQL Server Standard. There are a lot more...

2010-01-13

840 reads

TSQL Tuesday #2

by Grant Fritchey

The Scary DBA

I’ve wracked my brain for some bit of puzzle that I could present as part of TSQL Tuesday #2 and I...

2010-01-12

1,125 reads

Horror… sort of

by Grant Fritchey

The Scary DBA

You must read this post from Tim Ford to understand why I might do this on my technical blog. But...

2010-01-11

885 reads

New England Data Camp v2/SQL Saturdy #34 Update

by Grant Fritchey

The Scary DBA

The second annual New England Data Camp is shaping up to one excellent event. We’ve put together a great set...

2010-01-11

560 reads

PASS Summit Evaluations

by Grant Fritchey

The Scary DBA

The big day has arrived and all the speakers are poring over their PASS Summit 2009 evaluations, me included. These...

2010-01-06

699 reads

Be Prepared

by Grant Fritchey

SQLServerCentral.com

Editorial

Today we have a guest editorial from Grant Fritchey. The Boy Scouts motto is "be prepared" and most of you probably unconsciously follow that in your daily lives. Why is it that so many of us don't follow through on this same advice with our databases? Grant Fritchey gives a few examples of how you should "be prepared" for a database emergency.