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

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Read the latest Blogs

Forums

Changes, Happiness, and a Few Tears

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changes, Happiness, and a Few...

BCP on Linux

By Steve Jones - SSC Editor

Comments posted to this topic are about the item BCP on Linux

You Probably Don't Need a Vector Database

By Kumar Abhishek

Comments posted to this topic are about the item You Probably Don't Need a...

Visit the forum

Question of the Day

BCP on Linux

When running bcp on Linux, what is the field terminator?

See possible answers