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

SQLServerCentral Article

A Normalization Primer

For most DBAs, normalization is an understood concept, a bread and butter bit of knowledge. However, it is not at all unusual to review a database design by a development group for an OLTP (OnLine Transaction Processing) environment and find that the schema chosen is anything but properly normalized. This article by Brian Kelley will give you the core knowledge to data model.

(3)

You rated this post out of 5. Change rating

2003-01-13

18,702 reads

SQLServerCentral Article

Information Schema Views

SQL Server DBAs are often curious about the inner-workings of SQL Server. Indeed, it can save your job during disasters to know what's going on inside SQL Server. This article shows you how to use some of the SQL Server internal views to view some meta data about your servers.

(1)

You rated this post out of 5. Change rating

2002-01-09

17,556 reads

Technical Article

Report Locking on Specific Database

This Script reports locking on a particular database either to the console or to a database table. It also allows filtering based on a minimum locking level (say Page or Table and higher). Included is the CREATE TABLE statement to build the reporting table. This table can reside in any database but needs to be […]

You rated this post out of 5. Change rating

2002-01-06

1,026 reads

SQLServerCentral Article

Design Oversight - Preliminary Review

We all know what the ideal application design environment is for building a database back-end: an experienced DBA takes inputs from end users and developers and creates the database design in order to support the application being developed. But in reality, we don't get the opportunity to do application design like this very often. This article covers how to quickly find and fix problems in a design.

You rated this post out of 5. Change rating

2001-08-20

8,213 reads

Blogs

T-SQL Tuesday #192: SQL Server 2025 Backup Changes

By

I hosted this month, but I decided to put my own entry in as...

Why Databases Still Fascinate Me

By

I get asked a lot about why or how I began working with databases...

Monday Monitor Tips: ServiceNow Integration

By

Earlier this year I visited a customer that was using the Redgate Monitor webhook...

Read the latest Blogs

Forums

Member was not found in the cube when the string

By giles.clapham

Hey, I've not done a cube for many years but I find myself supporting...

Implementing PostgreSQL with Python for Real-Time Logging and Monitoring

By sabyda

Comments posted to this topic are about the item Implementing PostgreSQL with Python for...

Identify a Slipstream Installation

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Identify a Slipstream Installation

Visit the forum

Question of the Day

Identify a Slipstream Installation

I get a new SQL Server instance from my build team. How can I tell if the instance was installed using a slipstream installation later?

See possible answers