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.

SQLServerCentral Editorial

Be Prepared

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(2)

You rated this post out of 5. Change rating

2010-01-04

404 reads

Technical Article

Be Prepared

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2010-01-04

2,109 reads

Technical Article

Be Prepared

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2010-01-04

2,707 reads

Technical Article

Be Prepared

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.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2010-01-04

2,236 reads

Blog Post

Plagiarism

And really bad plagiarism at that.
I received an email from someone suggesting I check out a book on Lulu.com, that...

2010-01-01

1,032 reads

Blogs

T-SQL Tuesday #203: Risk and Reward

By

This is timely, as I’m currently on a boat in the Adriatic taking a...

dataMinds Connect 2026 – Slides & Scripts

By

You can find the slides and SQL scripts for my session “Spice up your...

How to Clear the SSMS Cache (SSMS 21 and Later)

By

How to Clear the SSMS Cache (SSMS 21 and Later) Updated...

Read the latest Blogs

Forums

Using CHOOSE()

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Using CHOOSE()

Re-Seeding a Broken Log Shipping Secondary (Without Touching the Primary)

By LukaMK

Comments posted to this topic are about the item Re-Seeding a Broken Log Shipping...

The DBA is Dead! Long Live the !

By Grant Fritchey

Comments posted to this topic are about the item The DBA is Dead! Long...

Visit the forum

Question of the Day

Using CHOOSE()

We have this code that sets some status values and then queries them using the CHOOSE() function in SQL Server 2025.

CREATE TABLE Status
(
    StatusID INT,
    StatusDescription VARCHAR(20)
);
GO
INSERT dbo.Status
(
    StatusID,
    StatusDescription
)
VALUES
(0, 'Uncategorized'),
(1, 'Active'),
(2, 'Inactive'),
(3, 'Temp');

GO
SELECT CHOOSE(StatusID, 'Unknown', 'Active', 'Inactive', 'Temporary')
FROM Status;
When the SELECT runs, what is returned?

See possible answers