Tag: syndicated

  • Down and Dark

    I came back from vacation to find the home DSL line bouncing up and down a bit. I wasn’t overly worried, and the kids knew to restart the router when it went down, crossing their fingers for a good connection. I suspected the router might be dying, and was getting mentally prepared to go hardware shopping. I figured I’d enjoy the downtime and stay unwired for the last few days before going back to work.

    On Sunday night, our connection was down for good, with a red light on the router. I called Monday morning into the Century Link tech support line, and they informed me they knew there was an outage. Good, I thought, they’ll have it fixed soon. I packed up and spent Monday in town working at the library to not fall any further behind.

    Tuesday morning had the line still down, despite complaints to Century Link. The people answering the phone apparently are not any more informed by their engineers than I am. I find that hard to believe, but there wasn’t much I could do. I packed up again, and am in town working again.

    Broadband access has almost become a commodity, and I’d argue that for many of us, it’s a utility. We pay bills online, get sent all sorts of information online, many of us not even getting newspapers anymore. It’s not longer a luxury, but a necessity for us to make do in the modern world. For me, it’s part of my job, and the lack of a line is a huge impact to me getting work done.

    Fingers are crossed that this gets fixed soon as work is piling up.

  • Almost an MCSA

    I took four beta tests earlier this year for SQL Server 2012. I had debated writing another book, and I’ve worked on a few of the cert books in the past, so I thought this would be a good chance to look at the tests. Since I had free invites to the beta program, I also thought, what the heck. The worst that can happen is I fail.

    It’s been about two months, and I was waiting for results when someone mentioned that the Prometric site had the results, though they weren’t yet up on the MCP site. I checked, and sure enough I had results for some of my exams. I checked a few days later, and found results for all four of my tests. They were:

    All passed, which was cool. I think certification is what you make of it, and I’ve been looking over lots of SQL Server 2012 stuff for almost a year, so to me it says I have some good knowledge of SQL Server 2012. The tests were a good mix of old and new stuff, and not as focused on the new features, which was good.

    The MCSA track for SQL Server 2012 needs 461, 462 and 463. I skipped 463 in the beta cycle because I’m not much of a DW person, and I was busy. Fitting in 4 exams across two weeks was hard, and took time away from work that I had to make up at night.

    I’m not overly concerned about being certified, but it’s a nice feather to have in your cap. The MCSE for SQL Server 2012 requires the MCSA and 464 and 465, which I have. So one more test and I’d have the MCSE as well.

    My goal now is to start studying for 463, after I get a few more presentations built that I need for work. I hope to get to this test in the fall, or perhaps at the end of the year, depending on my schedule. I haven’t done a lot with the DW side of things, so I’ll be working, and likely writing, about a few more DW topics later this year.

  • Holiday

    Sort of.

    I’m off for a week to Camp Alexander near Pikes Peak for Boy Scout summer camp. My 13year old is attending and working his way toward Eagle Scout. He’s a Star scout now, and with any luck, this week we’ll get 3 more of the Eagle required merit badges and be that much closer to that amazing achievement.

    There’s no cell service, and no real Internet, so I’ll be completely out of touch for a week.

    Everyone behave.

  • T-SQL Tuesday #31 – Logging

    TSQL2sDay150x150It’s T-SQL Tuesday time again, and this month Aaron Nelson (blog | @sqlvariant) is hosting. The topic is logging, and if you’re like to participate, read Aaron’s post and learn the rules. We do this on the second Tuesday of every month.

    If you’d like to host, contact Adam Machanic. It’s easy to do. Get on the schedule, pick a topic, and then write a post.

    A list of previous posts is here,

    Logging

    I’ve found documentation of events to be one of the most important things I can do in my career. Finding out what happened, what changed, or what I did has been important many times, and often helped me come through difficult situations.

    Logging is the automated version of documentation. All kinds of applications, including SQL Server, produce logs of the various activity on the system. In SQL Server, we are moving to an eventing system, and if you haven’t looked at Extended Events, you should.

    One of the times when I found logging to be lacking was in a startup I worked at a decade ago. We had a number of developers that were working on various development servers. They had full rights, and they were allowed to build their own objects. That was a little concern to a controlling DBA like me, but I allowed it since they often wanted new objects quickly, and if I allowed them to write their own, they’d use stored procedures.

    A good compromise, if you ask me.

    However in the hectic pace of development, I found that the developers didn’t often keep good notes about what was being built for which features and functions. Since we had to produce a build script fairly quickly every Monday in order to update our QA systems, we would find that developers invariably would forget objects and we would not have a well tested QA script on Monday afternoon.

    I decided that we needed to better log the changes on our development server. I didn’t care about every change, especially intermediate changes to objects, but I did care about the gross changes made each day.

    This was in the SQL Server 2000 days, with limited tracking of changes outside of SQL Trace. Since I had no desire to move through lots of trace files, even in an automated fashion, I decided on a much simpler method.

    In sysobjects (now sys.objects), there was a crdate field, which tells you when the object was created. However that doesn’t change if an ALTER TABLE is run (or any other ALTER). That stumped me briefly, but I decided to search further.

    I found that there was a schema_ver field, which is incremented every time the object is changed. Since the majority of our developer changes were ALTERs, I could track the version number and then compare this each day. I tested this out, and it worked well.

    The outline of the solution is that I grabbed a copy of the sysobjects table every day and stored it in a temporary table. I then used a left join to compare this with the previous values stored in a table I’d created to store the data. When I found differences, I logged them in a table, along with the date, and sent myself an email. I would then overwrite the stored version of the objects with the version from the temp table, giving me a baseline for the next execution.

    At the end of the week, I’d have an aggregate list of all objects changed, which I could then compare against our build script.

    At the time we were in an agile environment, releasing new code every Wednesday, and operating on very short timelines. The logging I did cut down on mistakes and allowed us to have a smooth release process that functioned for over 18 months, with code releases nearly every Wednesday outside of holidays.