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

Review: Typhon III from NGSSoftware

Every shop with any sort of IT organization should be scanning for vulnerabilities and issues with their systems and SQL Server is no exception. Security software vendor has a tool that can scan and report on all your SQL Servers is an easy to use product called Typhon III. Our security expert Brian Kelley takes a look at this product.

You rated this post out of 5. Change rating

2004-10-07

13,920 reads

SQLServerCentral Article

SQL Server Security: Dealing with Anti-Virus Programs

Do you run an anti-virus product on your SQL Servers? After all, it's recommended, more and more, that you run anti-virus on ALL machines you have. There's just too much stuff running around out there. But putting this on a SQL Server creates some interesting issues. Our resident security guru, Brian Kelley, looks at some of the things you need to consider when deploying anti-virus products on your servers.

(4)

You rated this post out of 5. Change rating

2004-05-13

23,853 reads

SQLServerCentral Article

SQL Server Security: Security Admins

As we mentioned before, Brian will be writing a column covering all facets of security. Turns out that there is so much to cover, he has agreed to write two columns per month! This article talks about the principle least privilege, why it doesn't always work, and some good info about removing the Builtin\Admin account.

(3)

You rated this post out of 5. Change rating

2003-06-27

21,150 reads

SQLServerCentral Article

SQL Server Security: The db_executor Role

Brian will be writing a monthly column for us on SQL Security, definitely a hot topic these days! He starts off by discussing the need for a built in db_executor role and how to grant permissions manually to achieve the same effect. Terrific concept, as granting table access can lead to bad things! If there is a security topic you'd like to see more info on, post a note to the article or email us at articles@sqlservercentral.com.

(7)

You rated this post out of 5. Change rating

2003-05-16

41,362 reads

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,749 reads

Blogs

5 Starter Projects for Your AI and Data Engineering Portfolio

By

Reading tutorials is fine. Shipping something is better. If you are trying to break...

The Book of Redgate: Taking Breaks

By

We work hard at Redgate, though with a good work-life balance. One interesting observation...

Database AI Agents: The Read-Only Rule

By

Fourth in a series on Ai and databases. What Read-Only Advisory Actually Means A...

Read the latest Blogs

Forums

Liability for AI Errors

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Liability for AI Errors

Running a Parameter-Sensitive Stored Procedure on a Secondary Replica

By abdalah.mehdoini

Hello , I would like to run a stored procedure on a secondary replica...

Pro SQL Server Internals

By Site Owners

Comments posted to this topic are about the item Pro SQL Server Internals

Visit the forum

Question of the Day

Running SQLCMD II

I run this command to start SQLCMD:

sqlcmd -S localhost -E -c "proceed"
At the prompt, I type this (the 1> and 2> are prompts):
1> select @@version
2> go
What happens?

See possible answers