Dan, here's another tool you and others may find helpful:
MACRO: Get List of KM Variables and Size
I'm not sure of the relationship between the KM Variables SQLite DB and the Variables plist (which I believe is the primary source that KM uses). and one has to wonder why have both? An old DB adage is that as soon as you store the same info in two different places, one of them will ultimately be wrong. 
KM has two structural design points that are not really well scalable:
- KM has a monlithic macro file that contains ALL macros. It gets continually rewritten with every little change you make while editing a macro. And the same goes for the KM Sync file.
- Same is true with KM Variables -- the plist file contains all variables and gets continually rewritten.
Using a single file to store all macros/variables also makes it very difficult to backup and restore a particular macro. To workaround this issue, I wrote this macro:
MACRO: Export (Save) Selected Macro
Several Mac apps have taken a hybrid approach, which I really like:
- Use a DB to store metadata for all items
- Store the actual contents of the item in a separate file/folder for each item
Databases are very safe to use. I've been using them, and creating apps based on them, for decades. It is a very, very rare event that a database becomes corrupt and unrecoverable. Today's databases are even more robust.
Sorry for taking the discussion a bit off-topic. I hope your delay issue is resolved.