I’ve got another webinar tomorrow. This one in conjunction with Clear Measure, who work with companies to build better software. This should be interesting as Jeffrey Palermo and I talk about the characteristics of organizations that are getting better at delivering software in general, with some specific focus on the testing and data side of ensuring your software works.
Register and I’ll see you tomorrow.
A customer was asking about SQL Prompt recently and how their history is stored and if it can be moved to another machine. This post shows how this works, and how you could move it. There is also a video walk through at the bottom.
Caution: This is history for your specific queries, and moving the database means you overwrite history on the new machine. Don’t do this to share code. Do this only if you are upgrading your own machine.
This is part of a series of posts on SQL Prompt. You can see all my posts on SQL Prompt under that tag.
History in SQL Prompt is a slightly hidden, but amazing piece of technology. A number of customers find it incredibly valuable to see the history of their queries, especially when they’ve gotten busy with a number of different pieces of code.
In SSMS, when SQL Prompt is installed, it is keeping track of what you write in queries. Don’t worry, this is local, and it’s on your machine. Let’s look at this.
Say I have a query window, like this:
I can’t remember who the users are, but I add a new query to this window, as shown here.
All that is captured in SQL History. In one of the menu bars in SSMS, you can see this listed with other Redgate products.
When I click this and open it, I see my query windows in the upper left, with the window text in the right, and below on the left, a timeline.
This is the latest version, but if I click down, I see the previous version without the SELECT.
I can go back further and see before I added the ALTER ROLE statement.
All of my data is stored in my local profile. I can browse the path under AppData \ Local for my user, and inside there is a Redgate folder. Under that is SQL Prompt 10 (or your version). If I sort by date modified, I see my SqlHistory.db file, which is the database of my SQL History in Prompt.
If I were changing to a new machine and wanted history to move with me, I’d copy this file to the new machine. Unfortunately, I can’t put this in a VCS, as the path is set.
As I cautioned above, this isn’t something you send to colleagues. This is an individual file of your work and only copy this to a new machine when you are upgrading, not trying to sync work. Use a VCS for proper code control.
This is a SQLLite database, and any tools that let you look at the data work. I have the sqllitebrowser tool on Windows, which works great. I can click “Open Database in this tool and browse to my file.
Inside here, I see my schema and tables and if I scroll down to the bottom of the QueryVersions table, I can see my query in the last entry in the Contents field. Note the query on the right looks like the one in SSMS.
If I click up a few, I see the other version.
No magic here, just good solid programming that saves you a lot of time and helps you deal with the chaos of software development and the frailty of the human mind.
If you haven’t tried SQL Prompt, download the eval and give it a try. I think you’ll find this is one of the best tools to increase your productivity writing SQL.
I made a video of how this works if you’d prefer to watch this. You can also see all my SQL Prompt Tips.
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:
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.
