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

Technical Article

Another Reason to Avoid Cross-Database Ownership Chaining

This past weekend we were moving database files around because we added new LUNs to an existing production cluster. We went at the old tried and true way, we detached the databases, moved the files, and re-attached the databases. That seemed to work well...

You rated this post out of 5. Change rating

2009-02-20

2,133 reads

Blogs

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...

Free Online Sessions – Building the €100 DWH and Indexing for Dummies

By

I’m giving two online sessions soon on virtual events that are free to attend....

Read the latest Blogs

Forums

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-...

Tables with a SPARSE Column and Consumption

By dbakevlar

Comments posted to this topic are about the item Tables with a SPARSE Column...

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