Chris

Chris started in computing and I.T. in the mid to late 1990's. After the dust had settled from Y2K, he found himself a bit more focused and working with database servers on the Unix platform. His first exposure to SQL Server was in 2007 and he has been working on that platform ever since. Chris is currently a Sr. SQL Server DBA in more of a DevOps role with a main focus on operational reliability, stability and performance. His specialty is automation. He truly enjoys the days he gets to spend building tools with PowerShell to help his fellow DBA's manage their ever growing SQL Server environment.

All authors

All authors

Blogs

Capturing My Own Metrics: #SQLNewBlogger

By

A customer was trying to compare two tables and capture a state as a...

Red Flags in Your Query (T-SQL Tuesday #200)

By

When I'm looking at a query, I bet it's bad if I see... a...

T-SQL Tuesday #200: When I Look at a Query …

By

This month is a milestone for T-SQL Tuesday. It’s number 200, which doesn’t sound...

Read the latest Blogs

Forums

A Quick Second Opinion

By Steve Jones - SSC Editor

Comments posted to this topic are about the item A Quick Second Opinion

Five Intelligent Query Processing Features in SQL Server 2022 That Quietly Tune Your Workload

By vgupta

Comments posted to this topic are about the item Five Intelligent Query Processing Features...

Checking the Error Log I

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Checking the Error Log I

Visit the forum

Question of the Day

Checking the Error Log I

On my SQL Server 2025, I want to search the error log from my T-SQL code for potential issues and then inform an administrator. What is the current way to easily query the error log?

See possible answers