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

All authors

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

All authors

Blogs

A New Word: Anderance

By

anderance – n. the awareness that your partner perceives the relationship from a totally...

Troubleshooting SQL Server – Starting with the Error Log

By

We’ve all been there. Someone walks up and asks, “Is SQL Server having issues?”...

From OLTP to Analytics: Bridging the Gap with Modern SQL Architectures

By

In the beginning, there was OLTP – Online Transaction Processing. Fast, reliable, and ruthlessly...

Read the latest Blogs

Forums

Work out closing balance using opening balance of prior month

By Bhagat

Hello, I think I need a recursive cte query but unsure of the logic....

The Security of Old Tech

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Security of Old Tech

Revisiting SQL Server Window Functions- A Practical Walkthrough

By Chandan Shukla

Comments posted to this topic are about the item Revisiting SQL Server Window Functions-...

Visit the forum

Question of the Day

Tables with a SPARSE Column and Consumption

True or False:  Tables with a SPARSE column consume more space than regular columns if most values are NOT NULL.

See possible answers