You can still register and join me tomorrow. I’ll actually be in Austin at the Redgate office doing the webinar, which should be interesting.
Send your questions, comments, and have some fun as we look at the results from our survey of 3500+ database professionals.
Recently I was doing a demo and a customer asked how I had linked my commit in Azure DevOps to the work item that existed. It’s easy, and tldr; it’s with the commit comment. This post shows how that works.
I’ve been working with Flyway Desktop for work more and more as we transition from older SSMS plugins to the standalone tool. This series looks at some tips I’ve gotten along the way.
Many people use GitHub and adding issues is easy. You go to the Issues tab, click “New” and enter details. What is required might vary by project. I have a public demo project here: https://github.com/way0utwest/FlywayNorthwind
My issues tab has a few items, but you can see one of the issues below. Note, I’m not proud of this, as I just added this for a demo. I didn’t really add enough detail for anyone to work off this. I’ll do better with other issues.
In any case, the thing to note is I have a #1 at the top, meaning this is issue #1. If I type a comment or note anywhere in this project and include #1, a link is created to this issue.
This is very similar to the technique I showed in Azure DevOps. Actually, it’s the same. I’ll make some changes for a products table and generate a migration script. When I go to the Version Control blade, I see the changes and I commit them with a message that includes #1.
In the GitHub code tab, I see my commit message, and the #1 is hyperlinked. If I hover over it, I see the issue.
In the Issue itself, I see a flow with the commit listed.
Now I’m not only tracking discussion and comments of the issue, I’m linking commits as well.
This is less a Flyway Desktop feature than a GitHub one, but you can access this from Flyway Desktop by writing good commit messages with Issue numbers.
Try Flyway Desktop out today. If you haven’t worked with Flyway Desktop, download it today. There is a free version that organizes migrations and paid versions with many more features.
I made a quick video showing this as well. You can watch it below, or check out all the Flyway videos I’ve added:
altschmerz – n. a sense of weariness with the same old problems that you’ve always had, the same boring issues and anxieties you’ve been gnawing on for decades, which makes you want to spit them out and dig up some fresher pain you might have buried in your mental backyard.
Many of us deal with problems over and over in our lives. Sometimes we just don’t have the energy or power to change them. Sometime we don’t know what to do with them.
Over time, this can wear you down. For me, I have all sorts of problems, fortunately overshadowed by the amazing things I experience.
As an example, I struggle with anxiety when starting some projects. Not all, but there are some that I don’t complete well enough, or need repeated repairing, and I get challenged to find a new approach or even re-repair something. Sometimes these are things I’ve delayed fixing, sometimes they’re maintenance that creeps up again, sometimes a thing broke. I get anxious and feel challenged, I worry I don’t do well, I don’t want to start and get stuck or stop.
Rebuilding trailer hubs is one of those things. I can’t decide if maybe the trailer is bent too much, but these keep happening and I wish they didn’t.
I certainly have other problems, but relatively few. I deal with altschmerz well some days, and not well others.
From the Dictionary of Obscure Sorrows
Next week on Jan 23, I’m part of a webinar titled “Navigating the database landscape in 2024: Shifting skills to match constant demands”. You can register today and join me live or see the recording.
Redgate has run various surveys in the past, often with a professional survey company that reaches a wide audience. At the end of 2023, we surveyed lots of people about the state of the database landscape, with a emphasis on how the world of the database professional is changing.
Ryan Booz, Beca Parker, and I will be discussing what we think of the results, as technical professionals. This is more of an informal chat, a discussion about some of the data that came back from over 3,000 professionals.
Join us Tuesday the 23rd for a discussion and feel free to ask your own questions of us.
Voice of the DBA 