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,731 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,582 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,029 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,215 reads

Blogs

Identity Columns Can’t Be Updated: #SQLNewBlogger

By

I’m not sure I knew identity column values could not be updated. I ran...

Rolling Back a Broken Release

By

We had an interesting discussion about deployments in databases and how you go forward...

A bespoke reporting solution doesn’t have to cost the earth

By

You could be tolerating limited reporting because there isn’t an off the shelf solution...

Read the latest Blogs

Forums

Can someone please explain what happens?

By skeleton567

I have mentioned this several times over several years.  Can someone please help me...

SELECT COUNT(DISTINCT) returns null when nothing is found instead of 0

By tim8w

SELECT COUNT(DISTINCT Component) AS Found FROM tblComponents WHERE(Component NOT LIKE '%[a-z]%') AND(LTRIM(RTRIM(Component)) = 'GM13622')...

Remotely Engineer Fabric Lakehouse objects: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Remotely Engineer Fabric Lakehouse objects:...

Visit the forum

Question of the Day

Creating JSON III

In a SQL Server 2025 table, called Beer, I have this data:

BeerIDBeerName
1Becks
2Fat Tire
3Mac n Jacks
4Alaskan Amber
8Kirin
I run this code:
SELECT JSON_OBJECTAGG(
    BeerID: BeerName )
FROM beer;
What are the results?

See possible answers