Flyway Desktop Adds Object History View to Track Schema Changes

The useful part

Object History Steve Jones, 2026-09-28 It's a small change, but a handy one. I've been working with Flyway and Flyway Desktop and helping customers improve their database development. Checking History In Flyway Deskop, I can see all of my objects on the Schema Model tab on the right side.

How it works

• I can flip through the various history iterations of code here, just as I did with Git, but I can do this while I'm doing development work in the same place I've capturing changes.
• However, sometimes there are complex changes, or you don't notice something.
• This is a summary of the changes, which in the chaos of work, can be helpful.
• Summary This a small improvement, but one that keeps you focused on the work: what changed.
• You get the flexibility you need to control database changes in your environment.

What to take from it

Here I've selected CustProc in the list, and at the bottom I see the current version of the code. My new changes are on the right, with green shading to highlight what I've changed in code. I also have the green shading on the right, where I've added a comment and removed a comma.

Example or evidence

• Once I do that, my change appears as a new commit for this object in the history.
• AI Sparkle It can be easy to sometimes see the changes made by a developer and understand them.
• In the upper right, there's an AI sparkle next to the "Explain this change".
• I wouldn't just trust this, but instead this guides me along the code to look at what's been removed and added, and this summary helps me double check that the code does this, and that I understand it.

Details worth keeping

Object History – SQLServerCentral Flyway Tips: Flyway Desktop (FWD) now includes the object history for different schema changes, so as you are evaluating how your changes might fit in with others, or you are trying to determine where something broke, you can see a list of historical changes. This post looks at checking history quickly in FWD.

Related coverage

• Dev: True upserts in an append-only world: ReplacingMergeTree and FINAL.
• Joshsoftware: Originally appeared on Josh Software.
• Dzone: There's an awkward moment in every agentic data project.
• Sqlservercentral: Redshift keeps its SYS_* monitoring views for seven days in cluster, which is fine until an auditor or an incident review asks for something older. Until now the usual...
• Sqlservercentral: SQL Server Transaction Log Forensics: Preserving Evidence During an Incident SQL Server Transaction Log Forensics: Preserving Evidence During an Incident This is the companion to Why sys.fn_dblog...