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

Why use XACT_ABORT?

By

This came up one day at my work when a developer was using it....

Using AI for Data Conversion

By

I’m sure I’ve never mentioned that I’m an amateur radio operator. Like Vegans and...

Advice I Like: Tipping

By

When in doubt, overtip – from Excellent Advice for Living This is close to...

Read the latest Blogs

Forums

Migration related issue

By LearningDBA

I migrated DB server from 2017 enterprise to 2019 enterprise. After the migration, every...

How Much AI Code Would You Use?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item How Much AI Code Would...

Browsing for Instances

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Browsing for Instances

Visit the forum

Question of the Day

Browsing for Instances

I have a SQL Server instance that is not listening for connections on port 1433. By default, all ports are locked down on my server, except for the SQL Server port. What can I do to allow users to connect to the instance without knowing the port?

See possible answers

Cookies on SQLServerCentral

This website stores cookies on your computer.

These cookies are used to improve your website experience and provide more personalized services to you, both on this website and through other media.

To find out more about the cookies we use, see our Privacy Policy