Do you like the Refresh Design functionality as it is now?
- Go to menu Application – Refresh Design…
- Select the correct server.
- Repeat for the next databases.
This is ok, as long as you don’t need to do this that often, and as long as there aren’t a lot of databases to refresh. If you’re like me, you also have databases with a lot of dependencies, different servers, development/test/production,… and then a little change you’d like to deploy ends in an RSI nightmare (t.i. if you didn’t drop dead of boredom).
There’s also the extremely dangerous combination of boring, repetitive work and precision expected.
There must be an easier way
Now enter the world of Refresh Divine: do this once:
- Build a design refresh profile for each application you’d like to refresh.
- Set the refresh order for the databases of the same database family.
After initial setup, you just have to grab a cup of coffee, select the refresh design profiles you’d like to apply and press a button!
The idea existed for a longer time, and was born out of frustration. At certain moments I need to refresh the design of up to 30 databases (who all have dependencies). This is a time consuming, boring and dangerous job (if you select the wrong server, you can screw up the design).
Then I found the C API solution from the Breaking Par website (this is probably there for ages, they talk about Notes R5.03! Breaking Par doesn’t even exist anymore…).
I used and changed this code to create a tool around it.
But wait, there’s already an existing alternative! After developing half of my tool, I wondered: “Hey, maybe there’s something on OpenNTF already existing!” (I know, a late reflex) and indeed, there is: DbRecompiler does the same thing and much more.
But there’s a different approach: where DbRecompiler targets for more options and features, my goal was simplicity, ease-of-use, easy to setup. Use it for 1 minute and you know how it works!
Still here? Hurry to OpenNTF Refresh Divine project page then!