VersionSQL 1.9 - Branching - VersionSQL Help

The birds are singing, flowers blooming, and VersionSQL is growing new branches 🌳 (in your version control system, that is). Gather up your fertilizer, because it’s the most agricultural release of VersionSQL yet!

(Got an itchy green thumb? Download it right now! Rather have the highlights in bullet-point form? Click here for a concise changelog.)

New growth:

Boughs
Twigs
- Branch Specification at Setup
- Commit Entire Server Instance
Bugfixes
Final Thoughts

Boughs

Branch Switching

Just like a tree stretches many branches in all directions to build support for the wide canopy of leaves that collect nourishing sunshine, so the database developer enacts many changes in constructing the infrastructure necessary for growth to the business 🌞

To keep things organized, save all of the changes for each discrete project to different branches. By examining individual branches, you’ll be able to clearly and distinctly monitor the progress of each endeavor, notice any bugs that creep in, and pick out the necessary scripts for deployment.

Far from digging in the weeds, with VersionSQL 1.9 you’ll leap from branch to branch with the poise and grace of our bushy-tailed friends 🐿️

👨‍🌾 Master gardener says: In a shared database scenario, many branches connect to the same tree. To avoid cross-pollination, review the list of changes every time you run a commit to ensure only those relevant to the current branch are included.

Thanks to Hilmi E, Phil P, and others for suggesting this feature.

Branch Creation

Too many changes happening in trunk 😵? Sprout off new branches for the junior developers to climb around in 👦 When they’re done you can use your version control system’s tooling to graft the changes back in. And if things get too knotty or gnarly, just lop that branch right off 🪓

📕 Farmer’s Almanac says: Deleting a branch of SQL code will drop changes from your version control repository, but those edits will still be present in the database. Take a look at the branch’s change history first to see what needs cleared out.

Extended Properties

Hidden as they are, deployment of SQL Server Extended Properties often leaves us stumped. Starting now, VersionSQL scripts out extended properties right along with the object that carries them, making transplanting a breeze 👍

Thanks Alon R for writing in to ask for this feature.

Twigs

Branch Specification at Setup

Living in a tree already? 🦥 Climb to the right branch from the start by calling its name during connection setup.

Important: The branch name you enter here must be spelled exactly the same as a branch already existing in the repository. To create a new branch, instead leave the Branch field blank during setup and use the Switch/Create Branch interface.

Commit Entire Server Instance

Careful branching works great for the arborist, but perhaps you’re more of a park ranger with an entire forest under your care 🏞️ Catalog the whole thing all at once!

1) Enable the experimental feature under VersionSQL → Settings:

2) Right click on the server instance and click Commit Entire Instance:

Note that this will skip any databases that have not yet been connected to version control, so do that first. Thanks Mark R. for the request.

Bugfixes

🐞 VersionSQL now blocks multiple simultaneous commits for the same database to avoid resource conflicts (file locking, etc.)

🦗 Trial status banner now updates immediately after license activation (thanks Tim!)

Final Thoughts

The best time to start version controlling your database was 20 years ago. The second best time is now. Plant a SQL seedling of your own and watch it grow into a beautiful tree: Download VersionSQL today 🌱