Voice of the DBA

Author: way0utwest

  • Branding, Encryption, and Yoga in Cleveland

    It’s just under two weeks to SQL Saturday #241 in Cleveland. This will be my second trip of 2014 and I’m doing some planning for the trip.

    First, Yoga.

    I practice yoga every week and find it to be a good workout as well as a relaxing one. It helps with my flexibility, and since I’m having surgery in a few months, I’m trying to make sure I continue to work muscles. Erin Stellato and I started planning on a class on Friday morning, Feb 7, 2014. It’s the day before SQL Saturday, but since I’ll be in town, it’s a good choice. Erin uses the Inner Bliss Yoga studios, and if you’re interested and want some #sqlyoga, come join us. I’m not sure which class we’ll do, but we’re leaning towards the 9:15 at the River studio. Watch for me to post details on Twitter.

    After yoga (and a shower), it’s time for SQL in the City 2014. We have our first event in the US taking place on Friday, February 7, 2014 at the Holiday Inn in Westlake. It’s free to attend, but we’d like you to register so we can plan for attendees. We have a limit, so please don’t register if you don’t plan on attending. We’ll be talking about database deployment, version control, and continuous integration. It’s an interesting topic, and one that lots of people find interesting and inspiring.

    Saturday is SQL Saturday #241. The schedule has me talking Encryption first at 8:45 and Branding at 11:45am. Please feel free to come to my sessions, or check out Grant’s Statistics or Query Optimization talk. Please also feel free to say “hi” or shake our hands at anytime. My apologies in advance that I won’t make the after-party Saturday night. I need to get home to Denver, so I’ll be leaving a bit before the end of the day to catch a plane.

    If you’re in the Cleveland area, join us Friday for SQL in the City and come on Saturday for SQL Saturday #241. There are also pre-cons taking place on Friday if you don’t want to see us talk deployment and would rather hear Argenis Fernandez talk about disaster recovery or Allen White talk Powershell. They’re both great presenters and $99 is a bargain for their pre-con events.

    Hope to see you there.

  • Just use Version Control

    There are free systems out there. If you have no budget, and want to get started, download one of these:

    There are good ones to pay for as well, and some of them have other features and integration you may like:

    There are plenty more. Please, please, please, start using Version Control. There are compelling reasons from many successful developers, including those that want your database code under control.

    There are ways to do this, but please pick one. Version control is a must for professional software developers. That means if you write code, and get paid for it, use version control. If you write code, and don’t get paid for it, value your time and use VCS anyway.

  • Servicing SQL Server in the Future

    Service Packs have become the way that many of us patch the various Microsoft products we use. Many administrators find patching to be time consuming and difficult to justify, even for security patches, and as a result, often wait for a Service Pack before they inform clients and schedule testing. Most people used to always wait for Service Pack 1 before installing a new version of a server product, but I don’t think that’s necessary anymore. The quality of Microsoft server products has gone up quite a bit in the last 5 years.

    However, I don’t like the way that the servicing, or patching, of products has evolved. For SQL Server, we get patches every other month, known as Cumulative Updates. Exchange Server has also moved to this format, though it seems many of the other server products (Windows Server, Sharepoint, System Center, etc) still release Service Packs. A few years ago it was rumored that Microsoft would not release Service Pack 3 for SQL Server 2005. A number of us voted on this patch and it was eventually released.

    The strategy announced at that time was that SQL Server would receive a service pack 6 months after the RTM release and thereafter annual service packs until support expired for the product. In between, Cumulative Updates would be released. That seemed to be the case for a few years, but once again Microsoft seems to have quietly decided not to move forward with Service Packs. We’ve been getting cumulative updates, but no service packs in over a year and a half. The last SPs we have are SP1 for 2012 (Nov 2012), SP2 for 2008 R2 (July 2012), and SP3 for 2008 (Oct 2011).

    If you’re like to express your opinion, take a moment and vote for these items:

    It just takes a moment to click on them, and I’d also ask that you pass along the URL (or this editorial) to friends that work with SQL Server.

    Personally I’d also like to see a solid strategy moving forward that includes annual service packs, especially with a 2 year release cycle. I know some of my fellow MVPs and writers like the CU strategy and wish more people would adopt it, but I don’t agree. It’s time consuming to test and prepare for updates, and as long as this paragraph appears on CU pages, I do not think we should recommend CUs to DBAs.

    “This cumulative package is intended to correct only the problems that are described in this article. Apply it only to systems that are experiencing these specific problems. The updates in this package may receive additional testing. Therefore, if you are not severely affected by any of these problems, we recommend that you wait for the next SQL Server 2012 service pack that contains the hotfixes in this package.”

    To me that shows even Microsoft doesn’t completely want to stand behind their cumulative updates.

    Steve Jones

    The Voice of the DBA Podcast

    Listen to the MP3 Audio ( 3.7MB) 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.

  • Powershell in a Month Day 13 – Remote Control

    This is part of my Powershell Challenge, to learn more about PowerShell (PoSh) using the Learn Windows Powershell 3 in a Month of Lunches book by Don Jones.

    Remoting. It sounds complex, and intimidating. It isn’t, and it’s powerful. It’s also essential, allowing you to access commands on remove machines.

    The chapter starts with the idea of remoting, and running commands elsewhere. We learn this comes from telnet and other remote type access, and is implemented as a web services protocol, WS-MAN. Incidently, this is how SSMS works. Your T-SQL is executed remotely on the server, not on your workstation. Lots of people don’t get that and get confused.

    This chapter presents a challenge. You need a domain for security to work correctly, or easily, with remoting. There are potential workarounds, but it’s an issue. I haven’t had a domain at home because of overhead and not wanting a domain controller set up. That means some setup work to build a couple virtual machines and create a domain.

    Ugh. Annoying, but it’s something I should do. I have wanted to rebuild a domain for some time, but haven’t bothered, but this is the excuse to do so. As such, I read the chapter, and started setting up the domain. That will take a few days, so I’ll continue on with the next chapter as I get a domain ready. More notes to come once that’s done.