I’m heading over to the Yardhouse (4th and Pike) as soon as SQL in the City is finished and should be there by 6. Andy Warren will likely be there earlier, so look for him. If you don’t know Andy, he looks like this:
This is me, though I’ll probably not have the horse.
Hope to see many of you there, especially new people attending the PASS Summit, or just data pros in Seattle.
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.
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.
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.
It’s linked with SQL Source Control to a local Git repository.
Let’s change something. I’ll pop open a stored proc.
Let’s make a simple, but real, change. I’ll add a NOCOUNT setting in there, which is a good idea.
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.
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.
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.
Once this is done, I once again see a clean Commit tab.
However, if I go to the remote repo, which is on GitHub in this case, I see my change.
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/
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.
Voice of the DBA 