Voice of the DBA

Category: Editorial

  • Pluralsight is Amazing

    I used to work for a digital learning company early in the modern Internet. We were ahead of our time and struggled to sell online learning at the turn of the millennium. Bandwidth limitations held back video courses from widescale adoption. I moved on when the company folded, but I’ve watched other companies start to build and grow video training across the years. One of them that I’ve been most impressed with is Pluralsight. In fact, I very much appreciate their customer service.

    I try to make time every week to watch something. I don’t always get to any bits of learning, which is the way things go. Life is busy, and some days I don’t have the mental energy. I do try to download a course or two to my phone for long plane rides and other travel. I’ve even had a few modules playing on long drives or in my headphones while skiing. Of course, I can’t watch the screen during those events, but I can listen and try to learn something on the go. I’ve even whiled away sessions on the stationary bike with a Pluralsight course playing in front of me. It’s not deep learning, but it’s a way of looking at something that I find interesting. I often will go back and try a bit of code later.

    I don’t focus too tightly on SQL Server with Pluralsight as I get plenty of that elsewhere, but sometimes I use their courses for investigation into other areas. I’ve listened to Chef and Puppet courses, C#, ASP MVC, Python, and more. I don’t always use the skills directly, but a little learning does help me understand the larger view of how technology works. I’ve found throughout my career that having some good general knowledge in various areas helps me troubleshoot and understand the larger picture, often helping me find an issue in a complex system quicker. I also get ideas on why I might consider some other type of technology as a way of improving an application in the future.

    I certainly hope that most of you continue to come to SQLServerCentral to get ideas, learn something, and get questions answered. My mission with this site is to help others become better SQL Server professionals. We may add some video to go with our written work, and certainly I think we could improve some assessments and testing. If there are areas you’d like to see more content, let us know.

    However, we can’t do what Pluralsight does with their long courses and variety of topics. If you get the chance, or have a subscription, check them out. They provide a great learning resource that I’d recommend.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Can Data Save the World?

    Years ago I read one of the Freakonomics books. It was an interesting look at how we might examine our world in unexpected ways, using lots of data. While I didn’t always agree with the conclusions of the authors in different areas, I did find the idea of using data to probe and examine for patterns in our world to be fascinating.

    Recently I caught a podcast with the authors, and the opening question caught my eye. It was “can data save the world?”, and I was hooked, needing to stop and listen to the episode. That’s because I think data is the most important asset in the world today, and data is what really powers all the software we have. We need data, and we need to ensure our data has a high level of quality and integrity in order to glean information from all those bits and bytes to get value from software. Certainly software matters, but data, to me, is more important.

    The authors’ position is interesting in that they see data as an important part of analyzing data. The type of data, industry, organization, etc. doesn’t matter, but the data also isn’t necessarily enough to change someone’s mind or convince them of an argument. There needs to be a story as well, which requires a different skill from that needed for analyzing data. I do think that often the way in which we present an analysis can be just as important as the data. Perhaps even more so.

    What I do find interesting in the podcast is that younger companies (and people) are willing to embrace more data driven approaches. I see that often. There have been no shortage of clients in my career that were sure they knew the answer to some question about their business job without referring to any data analysis. They trusted their experience. Even if there was data that might show their conclusions were slightly erroneous, they often didn’t want to change their decision or conclusion.

    Humans are creatures of habit. Even those of us that embrace some change will find that we like change in some parts of our lives, but not others. If someone has had success in their career without using data to support or alter their opinions, it can be hard to get them to change. I wish I had a good method for convincing people to get started using more data, but really I think that the best idea is to find a different person to convince. If you can do so, and produce real results, then you may be able to go back to the first person and show them some evidence.

    The one part of the podcast that I wish turned out different is at the end, where the authors note there isn’t a good way to teach someone how to analyze data and tell a story. They thought about creating their own curriculum, but gave up. It’s too much work, and apparently they weren’t sure they could do a good job.

    They imply this is harder than teaching someone to program, which is disappointing as we have lots of programmers that need help as well. If we can’t teach programmers at any scale, what does that mean for data scientists? The one part I would agree with them on is that data science is a great area to move towards your career if you have the talent.

    Steve Jones

    The Voice of the DBA Podcast

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

  • A Christmas Bug

    It’s not really a big deal for me, despite the fact that I travel to Europe in a few days for two weeks. At least, I’m fairly confident this won’t be an issue for me. A few of my fellow #sqlfamily might not be so lucky, as they use a different airline.

    Apparently American Airlines has a bug in their scheduling system. It’s not a safety bug, don’t worry about that, but it’s potentially a huge bug for the company in terms of profit and cost. The bug is a part of the system that lets pilots request holiday time off. The system allowed too many pilots to take vacation, and as a result, American Airlines (AA) doesn’t have enough pilots to fly their planes.

    In case you wonder about the scope of this, it’s 15,000+ flights that are affected. AA flies about 6,700 flights a day and are the world’s largest airline by some measure. They are offering pilots 150% of their normal rate, which is apparently the max allowed by contract. I’m sure some pilots will take the offer, but I’m also sure there may be some flight cancellations. After all, pilots have likely made their own plans, which they may not want to change. Apparently some have as the news as of this writing is a few hundred flights.

    The complexity of airline scheduling software has to be quite high, and while this won’t really endanger lives, it will affect the profitability of AA. This is definitely a development mistake, and one that should have been caught in testing. I don’t know how often this software is updated, nor what their process is. Someone suggested this is outsourced software, but that doesn’t matter. We clearly have a software development failure here.

    I certainly think developers are responsible for testing their code and meeting requirements. This includes not assuming the happy path is followed. However, this is also a place where we need (as an industry) to learn to better test the bounds and limits of our software. We need to be sure that we account for not only security, but pushing the limits of use by legitimate users. Software mistakes cost money, and as we continue to use computing more and more, we need to become better at testing our code. Our systems are very complex these days, more complex than a single person can handle. We need better testing everywhere, including the database.

    Please, make an effort to test better next year, in both your application and database. Use larger data sets at some point (both numbers and dates), add automated testing as a part of your development routine, and assume that users will do stupid, silly, and malicious things with inputs.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Not Useless Features

    Some time ago I noticed Adam Machanic had written a post titled The SQL Hall of Shame. In it, Adam notes there are features that Microsoft will introduce in SQL Server and then let die. These are the useless features that aren’t widely used, or even useful for many projects. You can read his list, and agree or disagree.

    I think there certainly are some features that were silly experiments and I wish they had been introduced as experimental, or beta, features early, allowing users to give feedback on whether they’re useful and where they need refinement. I certainly think too many resources were initially wasted on items like MDW and Query Notifications, and far too little investment later. These days I think we’ll see more early releases of items in Azure where users can experiment and provide feedback to help Microsoft decide if more investment is needed. At least, that’s my hope.

    Today I’m wondering if you think there are features in SQL Server that do need more attention. Those features you use, but appear forgotten and you’d hope they are improved in the next version.

    For me, I certainly wish replication would get more attention, tooling, and resilience. I’m not sure if this needs an overhaul, like SQL Server 2005 was, or there just needs to be some reworking of the code, but in today’s distributed world, we need a more reliable way to hook up portions of databases and move data around. Not ETL, not Availabilty Groups, a better replication architecture and implementation.

    There might be other features you use or want, but let me know today. What’s a not useless feature that you want improved.

    Steve Jones

    The Voice of the DBA Podcast

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