steve_jones.jpg

Steve Jones

Steve Jones is currently the editor of SQLServerCentral, employed by Red Gate Software. Steve has been working with SQL Server for two decades at a variety of large and small companies. Steve has spent time as a hiring manager as well as a technical DBA, easily moving back and forth between these positions at different employers. He has managed Windows networks, functioned as a production DBA, development DBA, software developer, and DBA manager. His work has included start-up as well as Fortune 1000 companies in the power, financial, education, and software industries. He currently has his dream job managing the largest SQL Server community on the Internet from his ranch in Colorado and writes a daily editorial at SQLServerCentral.
http://www.sqlservercentral.com http://voiceofthedba.wordpress.com/feed/

Sooner or later some sort of disaster occur on your SQL Server instance. It might be the destruction of a server, the corruption of a page inside the database, or just the unexpected deletion of some data. When disaster does strike, will you be prepa
A look at binary data in SQL Server and full-text searching of the content of binary files.
Everyone wants a job they enjoy and look forward to working at each day. This session will present practical techniques for improving your brand and giving you the chance to interview for the job you want.
Building software is hard, and we often find that fixing bugs is expensive if they are not caught early. Continuous Integration (CI) has proven to be a valuable technique in improving software quality and this session demonstrates CI for databases.
tSQLt is a testing framework that is designed to help you write repeatable, isolated tests against your database code. In this session we will briefly examine the goals of testing, and introduce tSQLt with a variety of demonstrations.
Everyone wants a dream job that they enjoy going to each week. Steve Jones will give you practical tips and suggestions in this session that show you how to better market yourself in today's competitive world.
Everyone tests their code, but most people use ad hoc, non-repeatable testing with simple queries. This session will show you how to begin implementing testing into your development process, giving you a growing library that improves code quality.
Come to this session to see how you can create a more efficient database development platform by integrating your VCS with SQL Server. In real-time, you’ll see how versioning, branching, merging, and the other manual tasks you hate can fade away with

Blog posts RSS

What’s Your Test Plan? 20 May 2016
I ran across a post on upgrading a SQL Server instance, where the original poster (OP) was asking about a document to upgrade from SQL Server 2008 to 2014. That’s a big ask, especially as not many documents tend to be written to go across three versions. The official ones, or the people that ...

The Complexity of Branches 19 May 2016
Branching code is hard.  Well, branching isn’t hard. Just right click in some GUI or or type “git branch” and off you go. The actual branching of code is pretty simple and painless. In some sense, branching might be too simple in today’s tools as developers are almost ...

Changing a Computed Column–#SQLNewBlogger 19 May 2016
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers. I was working with a computed column the other day, and realized I had the wrong definition. In this case, I was performing some large calculation, and the result was larger ...

Half Baked Features 17 May 2016
I gave a talk recently on some of the data protection features being added in SQL Server 2016, along with a few that have been available for some time. I think the talk went well, but I point out lots of potential issues with the features themselves. I had a question from someone that noted…

Software Maturity with Release Management 16 May 2016
For most of my career, releasing new versions of software that I or others had written consisted of manually running scripts or copying files, maybe using an installer once in awhile, but that was rare. In many cases, the process of actually deploying the software involved a developer sitting with ...