Brian Kelley

Brian Kelley is an author, columnist, and Microsoft SQL Server MVP focusing primarily on SQL Server security. He is a contributing author for How to Cheat at Securing SQL Server 2005 (Syngress), Professional SQL Server 2008 Administration (Wrox), and Introduction to SQL Server (Texas Publishing). Brian currently serves as an infrastructure and security architect. He has also served as a senior Microsoft SQL Server DBA, database architect, developer, and incident response team lead.
  • Interests: Chess, Reading, Soccer (Football), Baseball, Animals, Theology

External Article

Security Auditing Matching Up Logins And Users

I have been tasked with auditing security on my SQL Server. However, this needs to be a somewhat automated process as I don't want to have to rely on taking screenshots every month to satisfy our auditors. What tables and/or views should I be using and what's the best way to extract the information out of them?

2010-08-25

3,618 reads

Blogs

The GO Barrier: Why SSMS Multi-Server Query Waits for the Slowest Connection

By

I deployed a schema change to 30 servers using multi-server query and deploy-at-low-priority. Small...

10 Things I Hate About Fabric Deployment Pipelines— And Some Alternatives

By

Fabric deployment pipelines look like they solve CI/CD for Fabric content, especially for people...

The Book of Redgate: Evidence

By

We aren’t the only company that does this, but Redgate Software does try to...

Read the latest Blogs

Forums

A Challenge of Our Knowledge

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Challenge of Our Knowledge

The memory toll of VARCHAR(MAX) in SQL Server

By sabyda

Comments posted to this topic are about the item The memory toll of VARCHAR(MAX)...

Transaction Log Truncation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Transaction Log Truncation

Visit the forum

Question of the Day

Transaction Log Truncation

In SQL Server 2025, where can I find information about items that prevent or delay the transaction log truncation?

See possible answers