Voice of the DBA

Author: way0utwest

  • Getting RUN back in Windows 8

    Recently I heard a few people that note that they were really hoping the next update for Windows 8 will bring back the “Run button”, which was available in XP and Windows 7. I guess it was in Vista, but we won’t talk about that fiasco.

    I asked a question to the Intertubes and someone told me to do this:

    • Hit Windows+R
    • Pin the Run item to the taskbar.

    It’s that simple, and I tested it in Windows 8. It works well. Here’s what it looks like:

    Hit Windows+R, that’s the Windows key and the R button together. That gives you this:

    runbutton_a

    The Run dialog appears in the lower left hand corner. For me, that’s just above the IE icon (this is Windows 8, not 8.1, no Start menu button) and the last thing I ran is in there. I removed my item, but you will see what you last ran.

    Now, if you look in your taskbar, on the right side, you’ll see an icon that is the run dialog. In the image below, I’ve drawn an arrow pointing to it.

    runbutton_b

    If you right click this icon, you’ll get a menu.

    runbutton_c

    If you click “Pin”, then this icon will remain in the taskbar. You can click it anytime to get the Run dialog.

  • Getting Fired

    Have you ever been fired from a job? I hope most of you never have as it’s a somewhat traumatizing experience. I’ve been let go from one (and asked to leave another), and even though I didn’t like the job and wasn’t sorry to be gone, I didn’t like getting fired.

    Awhile back I saw Brent Ozar ask the question on Twitter: “when do you fire a DBA?”. There were a number of answers, and he ended up writing a post that summarized some of the reasons as responses. You can read the post, and the various reasons. I think for most of them, I’d disagree if any incident were the first occurrence of the situation. I know people will make mistakes, and if I don’t forgive accidents, I’ll never have anyone trust me as a manager.

    I also don’t think you let someone go for ignorance. They might never have had to deal with a situation. I don’t think you let them go if they don’t dig deep into systems and find problems. It’s always possible they haven’t gotten to the one item that causes a disaster.

    To me there are two certain places where I’d let someone go. The first is willfully taking part in any illegal activity. I don’t think an officer of an organization can allow that to take place. The second is more subjective. I would have to let you go when you’ve repeatedly shown that you’re not becoming a better employee and making the same mistakes over and over again.

    Failure to learn is not an option.

    Steve Jones

    The Voice of the DBA Podcast

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.

  • SQL Scripts Manager

    We have Down Tools Week multiple times per year at Red Gate. This allows various employees to spend a week on a project, working to build something new and interesting that we rarely have time to spend our limited resources on. Past projects have resulted in SQL Search, a mobile view of Simple Talk, and a number of internal tools that have proven very beneficial.

    Last year one of our developers embarked on a project for SQLServerCentral to provide a plug-in for Management Studio to allow access to the scripts on our site. This wasn’t quite complete enough to release, but when Down Tools week occurred recently, a few developers collaborated to complete this project.

    We’re releasing this Management Studio plug-in today, SQL Scripts Manager, along with our framework to build your own plugins.  You can download the tool from this link, and a link will also be placed at the top of our Scripts section at SQLServerCentral. Once you have this plugin installed, you can search for and download scripts inside SSMS, and access your briefcase without ever switching applications.

    I think this is really amazing, and I’m hoping that many of you find it useful. It’s a great way to easily access your collection of scripts from anywhere, getting the latest versions of the code from SQLServerCentral that you find really useful.

    If you have comments, suggestions, bugs, etc., please feel free to post them in this thread.

    We’ve worked hard at Red Gate to not only build useful tools that help you build software, but also teach you how to better create your own applications. We’ll have more information and more details on the framework coming soon as well, and we look forward to seeing what types of enhancements you’ll create for SSMS. If you create something really useful, send us a note and we’ll feature your tool on the site.

  • The Endless Upgrade Cycle

    Security posts are always interesting to me, and this one on Tesco security is no exception. It’s an analysis from the outside of a number of problems that are blatantly obvious with the way Tesco deals with passwords for their web systems. A great read, one that even your managers might use to better understand why some security processes should be followed. Developers certainly should read this as well, and I’d recommend this as one post to pass around.

    There is one point in the piece that I want to talk about.  In the post, Mr. Hunt mentions that the server software and development platform in use are old, 7 and 9 years old respectively. This section rightly points out that these technologies have been vastly improved, and security has changed. The company should have upgraded.

    Or should they? Obviously if they were really worried about the security of their systems they should have, but how often do they upgrade? When is the upgrade treadmill from software vendors a costly path with little benefit and when is it really necessary? I’d argue that some of the security issues in software should be back ported and fixed. After all, vendors sold these products with the promise they’d work and be supported. Microsoft offers 5 years of mainstream support and 10 years of security support, so at least for the web server, Tesco should be OK.

    I find myself torn on this issue. I certainly understand that software companies need to sell new versions of their products to maintain their businesses, but I also think they bear some responsibility for the security worthiness of their previous versions. Where and how we draw this line, I’m not sure, but I certainly don’t think the answer is as simple as “just upgrade.”

    Steve Jones

    The Voice of the DBA Podcast

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

    The Voice of the DBA podcast features music by Everyday Jones. No relation, but I stumbled on to them and really like the music. Support this great duo at www.everydayjones.com.