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

410 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

Blogs

Asking for Help Isn’t a Weakness

By

During COVID, I attended training on software/enterprise architecture given by Mark Richards. One of...

The Proof of the Backup Is in the Pudding

By

For me, the objective is straightforward: have a backup strategy that is reliable, understandable,...

T-SQL Tuesday #204 – Are blogs still relevant?

By

Note: This post is the invitation for T-SQL Tuesday #204 on November 3rd, 2026....

Read the latest Blogs

Forums

Alamat Telp BCA KCP Poris Indah (+62) 838-4945-0961

By Halo_BCA

Wa:083849450961 Ruko Poris Indah, Komp, Jl. Poris Indah Blok K No. 2-3, RT.003/RW.003, Cipondoh...

The ##MS_DatabaseConnector## User

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The ##MS_DatabaseConnector## User

Planning for Change

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Planning for Change

Visit the forum

Question of the Day

The ##MS_DatabaseConnector## User

On SQL Server 2025, I run this code as a sysadmin:

CREATE LOGIN Demo WITH PASSWORD = 'Demo1234567'
GO
ALTER SERVER ROLE ##MS_DatabaseConnector## ADD MEMBER Demo
GO
I then login as Demo and run this:
USE sandbox
go
SELECT CURRENT_USER
What is returned?

See possible answers