Voice of the DBA

Category: Blog

Friday Flyway Tips–Commit and Push

Flyway Desktop includes version control features with Git. One thing that was added in v6.5+ was the ability to commit and push.

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.

All in One Press

This isn’t a big change, but it is one that customers have asked for. On the version control tab, when you have changes, they are listed with a commit button in the lower right.

We’ve added a drop down to this.

If you click this, you now have commit or commit and push options.

Pick the lower one, and you’ll get things committed and pushed up.

The choice isn’t saved, which I think isn’t a great design choice, but for now, you do have the option with each commit.

Try it 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.

Video Walkthrough

I made a quick video showing this as well. You can watch it below, or check out all the Flyway videos I’ve added:

https://youtu.be/QsWVcYxFdnM

September 15, 2023
A New Word: Justing

justing – n. the habit of telling yourself that just one tweak could solve all your problems – if only you had the right haircut, if only you found the right group of friends, if only you made a little more money, if only he noticed you, if only she loved you back, if only you could find more time, if only you were confident – which leaves you feeling perpetually on the cusp of a better life, hanging around the top of the slide waiting for one little push.

I find a lot of people that have justing, thinking their are quick, easy solutions just out of reach. Of they focus so much on the one thing they desire, ignoring the rest of life. Or at least diminishing it.

I try hard not to have justing. In fact, lots of comedians have helped me to view the world differently. I accept where things are, I know there is chaos and struggle and other difficulties. I have to just accept and account for them, not wish things were different. Instead, I view the world as imperfect and not always here for me but still a place to appreciate and enjoy.

I can’t always get to the gym or I don’t always eat as well as I should. I accept that and work with it, not wishing it were different. I accept my faults and frailties, and I try to nudge them in better directions, knowing they will always be there.

I remind clients of this at work. There is no perfect way to build software, and you will always have some issues. You’ll always have some staff insufficiently trained, you’ll always have some people you don’t like. Work with that imperfection and don’t think about justing.

From the Dictionary of Obscure Sorrows

September 15, 2023
Creating Empty Repos in Azure DevOps–#SQLNewBlogger

I saw someone struggling with getting started with a Visual Studio project and Azure DevOps. They got a conflict, which I’ll show and then get you started with an empty repo.

Another post for me that is simple and hopefully serves as an example for people trying to get blogging as #SQLNewBloggers.

The Problem with Initialized Repos

First, I’ll open VS 2019 and create a new database project. I won’ t walk through that, but once I do, then I can add my project to source control. In the lower right corner, this is an option:

I’ll choose a local repository here. I see plenty of people do this if they don’t want to use GitHub.

Now, I go to Azure DevOps and create a project. I initialize that project with a Readme, which seems like a good idea. You can see my online repo below:

When I create this, I get the options to link an existing repo or push up.

However, if I try to link my existing local repo, I get an error.

Why? I have a commit in the report (initialized with a readme) and commits locally. That’s a conflict.

Creating an Empty Repo

The way to avoid this is make an empty repo in Azure DevOps without anything in it. When you see this screen, un check the “add a README”. No matter how much you want to have one, don’t do this.

Now, you have an empty repo for the remote. You should see this online, with the first line noting this is empty. From here, you can use the second box to push your repo from the command line.

SQLNewBlogger

This post was easy for me, but I’ve been in the situation where I’ve made this mistake. It’s annoying, but it’s also confusing as you should be able to make changes in both repos. That’s why we use git.

You can, but not when both are initialized. You need to clone one from the other.

This post took me about 15 minutes to create, with a good portion of time spent creating the scenario twice (two repos) and the db project in VS, which is slow. You could do this same thing and show how (and why) you set up a project linked to source control. If you use a couple systems (one at work and one at home) make two posts!

September 13, 2023
Webinar: The Cloud, the Future, and Bob Ward at the Summit

I’m doing a webinar next week with Bob Ward, a principal architect for Microsoft working on Azure and SQL Server. I’ve had the chance to work with Bob quite a few times over the years, and I’m honored that I get to host a webinar with him.

He has spent the last couple years doing a number of pre-con talks on SQL Server 2022 and how it integrates into a modern application. This year he has a pre-con on Monday at the Summit that looks at how you take your skills and move them to the cloud, with some hands-on experience in Azure. It’s not designed to sway you to Azure, but help you decide if it makes sense for your situation.

It’s a great opportunity to learn about the Cloud and how it works. In the webinar, we’ll discuss some of the concepts and rational for considering the cloud as part of your future career.

You can register here for our webinar next week. It’s Monday, Sep 18, at noon Eastern time.

September 12, 2023