Voice of the DBA

Category: Blog

  • Travel Confusion

    I confused myself. Twice apparently in October. Let’s hope that this one works out as well as the last one.

    Jones is a Good Name

    I flew to Orlando on Oct 8. I got a car, and drove up to my hotel in Lake Mary, near the SQL Saturday pre-con. I checked in, the lady asked for me name, acknowledged "Jones" and confirmed I was there for one night.

    I was slightly confused, but thought I might have booked a different hotel for the next night closer to the SQL Saturday. There are times I’ve got events in two places, so I stay near them. When I got to my room, I checked, and my phone showed a reservation for Oct 9-11, at the same hotel.

    Hmmmm.

    I went back downstairs and we determined I didn’t have a reservation for Oct 8, but there was another Jones coming. Apparently I got his or her room. We fixed things, I kept my room, and then promptly double checked the rest of my hotels in the UK.

    Check In is Available for Your Flight

    That was the message I got today when I came out of yoga. At first I started to check in, then realized today is Friday. I planned on going to Seattle on Sunday and I can only check in 24 hours in advance.

    A check confirmed it. I’d messed up reservations again. I called United and they said there was a bunch of space on a couple flights Sunday. If I changed today it was US$300. However if I want until tomorrow morning and call within 24 hours of the flight, there’s no change fee. The benefits of flying a lot are there, but not without some caveats.

    I created an appointment for myself in the am to call and change my flight. Let’s hope a bunch of people don’t book DEN->SEA between now and then.

  • SQL in the City Comes to Seattle in 3 Days

    Last week I spoke at SQL in the City 2015 in London, and it was a great event. We had a wonderful event, and I’m looking forward to Seattle. Lots of good questions and comments in my version control talk, good feedback on the keynote, which I really enjoyed. I thought our end of day panel was outstanding, and I wish we had 2 hours for that as the questions were amazing.

    I’m looking forward to a duplication of SQL in the City in Seattle on Monday, just a few days away. We’re going to be at the Hyatt in downtown Seattle, and we’d love to have you come. You can register and join us, but please don’t register unless you can come.

    There are also a few workshops in Seattle on Tuesday, so if you want hands on practice, come sign up for on of these.

  • Git Push in SQL Source Control

    I’m excited. Git support is growing in SQL Source Control and the release recently contains Git push/pull support. If you don’t see the release of 4.1.x, you need to update. The update should be available for everyone.

    I do like Git. I’m working with SVN, TFS, and Git on a regular basis. However I tend to prefer Git overall. Now I can do most things I want to do in SOC, which is exciting. No forgetting to push or the need to drop to the command line or another interface.

    The Git Additions

    In a previous post, I set up a link between a database and a Git repository. Let’s see how the Git push now works.

    I’ve got this database on my local instance.

    soc_git_push_2

    It’s linked with SQL Source Control to a local Git repository.

    soc_git_push_3

    Let’s change something. I’ll pop open a stored proc.

    soc_git_push_4

    Let’s make a simple, but real, change. I’ll add a NOCOUNT setting in there, which is a good idea.

    soc_git_push_5

    In the Commit tab for SQL Source Control, I see my change. Note that most everything looks the same here and I can see the code differences like I always could.

    soc_git_push_6

    Now I commit this change. In this case, it goes to my local Git repo, but isn’t pushed.

    NOTE: In the real world, I’d pull before I commit to be sure I wasn’t causing a merge issue.

    Once that’s done, my Commit tab changes.

    soc_git_push_7

    SQL Source Control (SOC) detects the change and knows we have an unsynced Git repo. I can now push the “Push” button. Once I do this, I get a warning if I haven’t turned this off. I turn it off, but you should always be aware that SOC isn’t managing your Git repo. It’s linking to it. If you make changes in the repo with some other app, like Visual Studio, the entire repo is pushed, not just the change SOC committed.

    soc_git_push_8

    Once this is done, I once again see a clean Commit tab.

    soc_git_push_1

    However, if I go to the remote repo, which is on GitHub in this case, I see my change.

    soc_git_push_9

    I love Git. I think it’s really cool, and it’s a great way to work with distributed Version Control. I am playing with TFS as well, but I prefer Git, and I think this support is great.

    There are still things needed, things I want, and more, so be sure you add your votes to the SQL Source Control UserVoice page and let the SOC team know what’s important to you.

    If you’re not using SQL Source Control, you might check it out and give it a try for a month: http://www.red-gate.com/products/sql-development/sql-source-control/

  • A Week Before Networking at the PASS Summit

    It’s a week before the Networking Dinner at the PASS Summit. Andy Warren and I are hosting the event next Monday, October 26th, at the Yard House in Seattle. The address is at 4th and Pike, just a few blocks from the convention center.

    Register here if you can come.

    There’s no cost, other than you covering your own food and drink expenses. We would like registration just to try and ensure we have enough staff at the restaurant.

    This is a great chance to network with fellow data professionals. If this is your first or second time at the PASS Summit, please come and meet some people.