Ken Johnson


SQLServerCentral Article

Securing the SA Account in SQL Server 2005

SQL Server 2005 has greatly changed the security paradigm for SQL Server DBAs. The sa account still exists, but for many tasks
you can now avoid using it. New author Ken Johnson brings us some ides for properly securing this highly privileged account.

(5)

You rated this post out of 5. Change rating

2008-02-20 (first published: )

16,605 reads

Blogs

The First Steps: Understanding the Basics of FinOps

By

As a DevOps professional, I’ve seen firsthand how cloud costs can quickly spiral out...

Monday Monitor Tips: AI Query Analysis

By

AI is everywhere. It’s in the news, it’s being added to every product, management...

AI: Blog a Day – Day 8: RAG – Retrieval Augmented Generation

By

RAG — Retrieval Augmented Generation. we have covered so far — embeddings, vectors, vector...

Read the latest Blogs

Forums

India's top water testing laboratory is FARE LABS Pvt. Ltd.

By farelabs

FARE Labs Pvt. Ltd., a water testing facility accredited by the NABL, tests drinking...

would it be so terrible to install ssms on a few user desktops?

By stan

Hi, ssms is free here.   I can think of other reasons to do this...

I'm thinking about submitting some articles

By Doctor Who 2

I've written some documentation on using different Markdown types of files on GitHub. It's...

Visit the forum

Question of the Day

Restoring On Top I

I am doing development work on a database and want to keep a backup so I can reset my database. I make some changes and want to restore over top of my changes. When I run this code, what happens?

USE Master
BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak'
GO

USE DNRTest
GO
CREATE TABLE MyTest(myid INT)
GO
USE master
RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACE

See possible answers