External Article

How to Get SQL Server Security Horribly Wrong

It is no good doing some or most of the aspects of SQL Server security right. You have to get them all right, because any effective penetration of your security is likely to spell disaster. If you fail in any of the ways that Robert Sheldon lists and describes, then you can't assume that your data is secure, and things are likely to go horribly wrong.

Blogs

Are you getting value from your reporting?

By

Do you spend so long manipulating your data into something vaguely useful that you...

The Book of Redgate: SQL Server Central

By

It was neat to stumble on this in the book, a piece by me,...

Git forked

By

Forgive me for the title. Mentally I’m 12. When I started my current day...

Read the latest Blogs

Forums

Microsoft Security Changes and SQL Server

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Microsoft Security Changes and SQL...

Expanding into Print

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Expanding into Print

Downtime Caused by the Postgres Transaction ID Wraparound Problem

By Chandan Shukla

Comments posted to this topic are about the item Downtime Caused by the Postgres...

Visit the forum

Question of the Day

The String Distance I

In SQL Server 2025, what is returned by this code:

SELECT EDIT_DISTANCE('Steve', 'Stan')
Assume preview features are enabled.

See possible answers