Steve Jones

My background is I have been working with computers since I was about 12. My first "career" job in this industry was with network administration where I became the local DBA by default. I have also spent lots of time administering Netware and NT networks, developing software, managing smaller IT groups, making lots of coffee, ordering pizza for late nights, etc., etc.

I currently am the editor of SQL Server Central and an advocate/architect at Redgate Software. I am also the President of SQL Saturday, maintain the T-SQL Tuesday monthly party, and remember our colleagues at sqlmemorial.org.

You can find out more about me on my blog (www.voiceofthedba.com) or LinkedIn (www.linkedin.com/in/way0utwest)
  • Interests: yoga, reading, biking, snowboarding, volleyball

SQLServerCentral Editorial

Unethical or Just Sneaky

One of the fundamental rules of a stable, controlled production system is that you apply updates singly, after they've been tested, and you document the change. This way you can ensure that if a problem occurs, you can do some backtracking to see what might have caused instability.

5 (4)

You rated this post out of 5. Change rating

2007-09-17

1,208 reads

SQLServerCentral Editorial

Recruiters

Do you like recruiters? Do you use them? It's almost impossible not to use them these days when looking for a job. So many of the listings on online job boards are from recruiters and many have deals to place people, so chances are you'll at least deal with on even if they don't get you a job.

You rated this post out of 5. Change rating

2007-09-13

174 reads

SQLServerCentral Editorial

What Could Go Wrong?

It's the law of unintended consequences: things happening that you don't expect from a seemingly unrelated area. This article talks about a data center having leaks from carpet cleaning above. The concrete floor had aged and the carpet cleaners dumped water on the carpet to soak it through and it leaked. I'm not sure how people have data centers below office floors, but I know I've had a number of them at different companies where I've worked.

You rated this post out of 5. Change rating

2007-09-12

141 reads

Blogs

Time to Revive our YouTube Channel

By

It’s been forgotten about and neglected for few years but I’ve decided to dust...

Microsoft MVP 2025: Continuing the Data Platform Journey

By

I am honored to announce that I have been renewed as a Microsoft MVP...

What is KTLO? Keep The Lights On vs Project Work in Agile

By

🔍 Demystifying KTLO: A Deep Dive into Keep The Lights On Work in IT...

Read the latest Blogs

Forums

How a Legacy Logic Choked SQL Server in a 30-Year-Old Factory

By Chandan Shukla

Comments posted to this topic are about the item How a Legacy Logic Choked...

Navigating Multi Platform Realities in My Database Life

By dbakevlar

Comments posted to this topic are about the item Navigating Multi Platform Realities in...

Import/Export SSMS Settings issue

By Brandie Tarvin

I have tried a number of times to export and then import my SSMS...

Visit the forum

Question of the Day

Query Plan Regressions --

For the Question of the day, I am going to go deep, but try to be more clear, as I feel like I didn't give enough info last time, leading folks to guess the wrong answer... :) For today's question:  You’re troubleshooting a performance issue on a critical stored procedure. You notice that a previously efficient query now performs a full table scan instead of an index seek. Upon investigating, you find that an NVARCHAR parameter is being compared to a VARCHAR column in the WHERE clause. What is the most likely cause of the query plan regression?

See possible answers