Voice of the DBA

Category: Editorial

  • A T-SQL Code Testing Guide

    Do we need a guide for code like this one? The piece linked is from a programmer at Google who gives some code review items that should be tested for. I’m wondering we we might want to have something similar for T-SQL code?

    I’ve given a few talks on how I to get started with tqslt, which is a great framework for unit testing T-SQL code. As I’ve learned more about it, and experimented, I’ve been amazed by how flexible it is and how it makes it easy to setup and run tests on T-SQL code. However I can only experiment with the way I code and the tests I think of, and I’m sure there are many other ways in which we can better verify that our queries work as expected.

    Testing has changed since I developed software in VB and C++. It seems that much thought has been given to building better unit testing that can not only catch bugs, but also ensure the code performs as we expect it to. There’s also the idea that we can run these tests in an automated fashion. That helps prevent some bug when we first write code, but it more often ensures code continues to work as we re-factor our work and enhance our applications. More and more I think that the constant and continuous regression testing is at least as important as initial testing, if not more so.

    I really hope that we improve our development processes and testing methodologies for SQL code. It seems that it’s an area where we can also increase the speed at we build better database applications, and improve the quality at the same time. If any of you are formalizing the testing of your T-SQL code, we would be interested in publishing your thoughts and results for others to learn from. Please feel free to submit an article.

    Steve Jones

     

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.5MB) podcast or subscribe to the feed at iTunes and LibSyn. 

  • The Next Five Years

    On one hand, the next five years don’t seem too far away. Five years, that’s a year more than most of us spent in high school or college. On the the other hand, 5 years ago was a long time in the computer world. Azure first gave us the ability to create a database, as opposed to just a key value store. SQL Server 2008 was the current version of the platform. SQL Saturday #26 was held the first weekend in October in Redmond. 8GB was the large size for flash drives and the iPad hadn’t started the current tablet revolution.

    The world of data has grown dramatically in 5 years. Our cell phones and other devices are drastically changed the amount of data that is collected and consumed. Advances in bandwidth have almost removed the need for us to move all but the largest sizes of data without any physical media. If we look to the next five years, does anyone think they can accurately predict how much storage we’ll maintain in our pockets or how fast we’ll expect to move data on a daily basis?

    I ran across a prediction of surprising things in the next five years, and while I’m not sure I think they will all come true, I do think that similar things will come to pass because of two things: amazing increases in computational power available to any individual and tremendous amounts of data. That’s no great surprise, but I am excited. I can’t help but think that there will be so many opportunities for data professionals that most of us will be gainfully employed for decades.

    I do think, however, that the mundane, easy jobs of administering individual instances, checking logs and backups, and setting security will be few and far between. Unless you know how to do those things for thousands of instances at a time.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.5MB) podcast or subscribe to the feed at iTunes and LibSyn. 

  • Saving Hard Dollars

    This week I ran across an analytics piece that talks about how Big Data and analysis can do more than help marketing, it can also create hard dollars for your company. Companies are using sensors and technology for mundane tasks, but tasks that can save the company substantial, hard dollars.

    You may have heard of UPS and FedEx optimizing their routes, and tracking the actions of drivers. Those companies (and others) have learned that a little programming work to analyze and create instructions for their workers can reduce wasted time and fuel, which ultimately means less wasted money. Other companies have reduced their heating or cooling costs with more data and small investments.

    I don’t know how many additional cost reductions can take place in most companies, but there are likely changes none of us have thought of that could be easily implemented with technology. It seems like a no-brainer that technology can build better routes, but early on, it wasn’t considered as an option because it didn’t replace a formal manual process. It wasn’t worth paying someone to design routes each day for a truck.

    As computer power increases, and more data becomes available, I predict that we’ll find many ways to analyze that data and change the way we run businesses. Many of the ideas will be unexpected, and some may be counter-intuitive, but those of us working with data will have a front-row seat to the ways in which data analysis can transform our world.

    Steve Jones

  • The Decline of SQL Server

    For many years in my career, SQL Server was the runner up. Both Oracle and DB2 were in much wider use and more popular among all sizes of companies. Serious applications used one of those platforms, according to many technologists, the DBAs on those platforms made more money, and most companies were willing to pay for the software. That changed, and over the years I’ve seen SQL Server grow close to Oracle, while DB2 has declined (and MySQL has grown). Here’s the 2014 chart from Gartner, on of all places, the MySQL site.

    I see other charts and reports, showing various percentages, so it’s hard to be sure where things stand. Many of them agree that for total market share, it’s still Oracle and DB2 (mostly on larger hardware), but SQL Server rounds out the big 3. However is that the case for jobs and opportunities? I read a piece from Thomas Kejser that pointed out that the popularity of SQL Server may be declining (there’s also an update).

    I see lots of jobs posted, and so many companies using SQL Server. SQL Saturdays continue to have great attendance, so I wanted to ask you this week:

    Is SQL Server being used less, or are other platforms being implemented, in your experience?

    Are you seeing a trend away from new, or additional, SQL Servers in your organization? I haven’t heard of any large trends, though I certainly do know that some organizations are considering other relational platforms. I think that’s healthy and expected. The technology for managing transactions is well known, and I think that all three major platforms, as well as MySQL and PostgreSQL are maturing to the point that any of them can handle the load for most applications out there.

    I think it’s only natural that other platforms will be used to solve problems that they are well suited for. However just as I don’t think SQL Server will grow to dominate the RDBMS space, I don’t think that NoSQL platforms will dominate over RDBMSes in many applications.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 2.9MB) podcast or subscribe to the feed at iTunes and LibSyn.