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.

5 (3)

You rated this post out of 5. Change rating

2003-01-13

18,679 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.

5 (1)

You rated this post out of 5. Change rating

2002-01-09

17,547 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,025 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,211 reads

Blogs

Advice I Like: Praise

By

Don’t reserve your kindest praise for a person until their eulogy. Tell them while...

How to Install SQL Server 2025 RC0 on an Azure VM

By

I wanted to try out the new JSON index which is for the moment...

Prepping for Certification, Part 1 of ?

By

I thought it would be good to put my thoughts down on how to...

Read the latest Blogs

Forums

Learning a New Language

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Learning a New Language

is there a way to "detect" schema like changes on a server?

By stan

Hi, we have a few people who like to experiment on our prod sql...

Guidelines and Requirements

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Guidelines and Requirements

Visit the forum

Question of the Day

Copying Production Schema

If I use DBCC CLONEDATABASE, can I remove some of the information from the copy?

See possible answers