Voice of the DBA

Category: Editorial

  • The Forever Technology War

    The Forever War is a classic science fiction novel. I’d highly recommend it if you enjoy that genre, but even if you aren’t a science fiction fan, this is a story that can really make you think. The gist of the story is that as various parts of our military travel faster than light, we might encounter foes (or other units of our own military) that are substantially ahead of, or behind us, in technology. All because of the nature of time travel. Recently I ran across a few situations that reminded me of this story.

    The first item was at home, where my son’s computer acted up. He likes Windows 7 and has stuck by it. However an update caused boot corruption and he wasn’t able to repair the system. In the process of trying to get repair things, we dropped into the command line to run chkdsk and bootrec. He wasn’t sure how those worked, which makes sense. He’s 17 and most of his life has been spent in GUI OS’s. However, once we realized he needed to reinstall, I told him to copy things off his boot drive to another drive. I showed him a bit of moving around the command line, making directories, listing contents, copying files. As I was walking away, he asked, “how do I make a folder?”

    A folder. Not a directory. We’ve had not only a technology shift, but also a nomenclature change in computing. It had never occurred to me that my son wouldn’t know basic command line calls. As a side note, he greatly appreciated the /? parameter to learn more about commands.

    The second situation was at a conference, where I was talking about continuous integration and deployment. A person asked about SSIS packages, and how would you move these with a tool like TeamCity or VSTS. I asked how they’d do this manually, and said that we would just program that. This person asked how they’d program the steps they take in SSDT. My answer was to use the command line, but this person had no idea there was a command line. Their whole career had been spent in GUI systems and they assumed that was the only way. Hint, pretty much everything can be run from a command line.

    Those situations showed me that we have a technology shift in place. There are things that some of us have grown up with, used as a base to learn more, and we can assume that others have similar paths. After all, wouldn’t you need to know about x to learn about y?

    Not necessarily. The longer I am in this business, the more I see that the experiences and knowledge of different people can be vastly different. A person that knows how some technology, say T-SQL and SQL Server security might have no idea how replication works. Or they might know AlwaysOn well, but couldn’t implement an Extended Event session. There are gaps and holes in the knowledge that each of us has, and assuming that others have similar understanding of any particular item can cause us problems when we try to work together.

    Understanding, transparency, sharing knowledge, and appreciation of diverse experiences can help us all learn, and work together better. If a situation seems strange or a person is confused, perhaps a few questions on their frame of reference of the situation is a better response than assuming they are incompetent or telling them to RTM.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Wasting Time

    This editorial was originally published on Oct 11, 2012. It is being re-run as Steve is on vacation.

    I ran across this infographic on wasting time at work. From the title I was thinking this would point out the ways in which people avoid work, and perhaps it does, but it’s really geared towards showing us the framework and structure that many people have for work. I agree with the first two sections of the page that show email and meetings waste a lot of time. I certainly think they have in many jobs for me, especially when they are used as “catch-all” techniques for including everyone that is remotely relevant to an issue.

    Interruptions at work are hard to quantify as a problem. They definitely can be, but stopping by someone’s office to ask a question or take a quick break can be a way to recharge yourself between long periods of concentration. The issues come into play when the other person is in the middle of focusing on a task and you force a context switch on them. Recovering from the interruption can take time, time that’s often wasted as a person tries to remember exactly what they were focusing on.

    Meetings certainly interrupt the day, but since they are often planned in advance, you can be mentally prepared for the break. It makes me wonder if there wouldn’t be some benefit to scheduling some “open time” in your day where you plan on taking a break. Others that needed a minute of your time would know to come find you at that time.

    Time is very valuable, one of the most valuable resources we have at work. Management should be aware of this and working to limit interruptions, whether through email, meetings or anything else that prevents work from getting done. The fewer meetings and emails you require of your developers, the more time they have to work on the tasks they are being paid to complete.

    Steve Jones

  • Your Technology Budget

    After I wrote about a home lab recently, someone was curious about the amount of money that others invest in their technology lab, habit, or hobby. I thought that was fairly interesting, so I decided to ask others to get an idea of what amounts people spend and even on what.

    How much do you spend on technology in a year?

    Let’s skip cell phone and Internet service bills, but if you buy cell phones, tablets, computers, Kindles, or other gadgets, let us know. I’d be curious about your spending on your career, which might be travel and events, training, books, etc. versus the spending on technology for fun.

    For me the amounts vary dramatically. The vast majority of my spending on technology is for replacement pieces and parts. I will buy hard drives or monitors or memory, but rarely anything more fun in most years. I don’t spend too much on learning as I get a Pluralsight subscription, and of course, I read SQLServerCentral. I rarely take training, but my generous employer usually covers that. In fact, most years, my total expense for technology is likely a few hundred dollars at the outside.

    I have purchased a few Kindle devices for reading, and I’ve gotten cases and batteries for my cell phones. I do go through keyboards and mice every year or two, sot hose are expenses, but rarely anything more interesting. I did buy a Pebble watch a few years ago. This year was an exception as I spent a bit to rebuild a desktop that has been aging. I didn’t get everything I wanted, but I substantially improved the speed, which was the important thing. I’ll also likely add in a new tablet next year to replace my aging iPad Mini (non Retina) to help with coaching volleyball. I’d like a drone for some fun camera work with kids and sports, but I suspect that is not likely to happen in the next year. Those gadgets are expensive for a complete indulgence.

    Let us know this week what you’re spending money on in technology and if any of those items have proven themselves really valuable, or just lots of fun.

    Steve Jones

    The Voice of the DBA Podcast

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

  • Where Do You Run Your R Scripts?

    I know most of you don’t work with the R language. In fact, plenty of you might not know anything about R other than a cursory understand of this as some sort of data analysis language. If you want to know more, here’s what the R Project is.

    Microsoft wants you to use R Services in SQL Server, or the R Server product available as a standalone system. However, I saw someone ask the question why would someone run their R scripts inside SQL Server, because these are expensive CPU cycles to burn on analysis. Someone else noted that Microsoft loves your licensing dollars, so their push to use R Services is perhaps a little self serving.

    Push the intellignce to the data makes sense. Isn’t that what we do with large data warehousing queries or SSAS cubes? We’re trying to get the analysis done at scale without having to move the data elsewhere, especially considering we’ve (usually) already moved the data in some sort of ETL (or ELT) process. Gaining insights from our ever increasing scales of data requires some computational cycles somewhere.

    What’s the alternative? Large queries that pull data to some client? I think that’s fine, and that might be a better alternative since simple queries to pull data don’t burn as many CPU cycles as those that might perform analysis. I certainly understand that the licensed CPU cycles for a SQL Server instance are expensive, and we want to be careful how they are used. Adding complex R scripts might not be the best use of our licensing dollars. On the other hand, if I can perform analysis quicker, that is more useful, than perhaps I can eliminate other random queries analysts want to run on my database?

    Ultimately I think that R Services make some sense in SQL Server, but not as some experiment. I would suggest that the R client is the way to experiment, preferably on a copy of data that allows someone to build scripts and determine if there is insight to be gained from a particular set of data. Build a Proof of Concept (POC), and only deploy it to a SQL Server if you find it provides value.

    And if you do so, continue to experiment. That R script you run today might not be as useful in six months as your application, database, and business evolve. Data analysis isn’t a set-it-and-forget-it, but rather an ongoing, iterative process.

    Steve Jones

    The Voice of the DBA Podcast

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