Database Repair fixes missing or broken file references in VirtualDJ’s database — the master record of every track VirtualDJ knows about.

When to use it #

Use it when tracks show as missing in VirtualDJ, a drive letter has changed, files were moved, or folders were renamed. This is almost always the right place to start a repair session, since the database is what everything else in your library refers back to.

What it repairs #

Missing or broken file references inside the VirtualDJ database itself. It doesn’t touch playlists, folders, or history directly — those are handled by CrossRef once the database is sorted, or by their own repair pages if you need to target them specifically.

How it works #

Like all repairs, Database Repair runs through four stages: export lists everything that looks broken, autofix can propose likely replacement paths, you review those proposals in the workbook, validate checks everything is sound, and import writes the confirmed changes back into VirtualDJ.

Key arguments #

• /repair:database
• /stage:export, /stage:autofix, /stage:validate, /stage:import
• /scan, /filter, /include, /exclude

Example commands #

vdjtools /repair:database /stage:export /filter:notfound
vdjtools /repair:database /stage:validate
vdjtools /repair:database /stage:import

Safety notes #

Take a backup first. Always validate before you import — it’s your last checkpoint to catch a wrong proposal before it’s written back to VirtualDJ. Once the database is fixed, CrossRef is usually the natural next step.

Limitations #

Low-value missing songs with little metadata may be skipped, since there’s not enough to match against confidently. AutoFix proposals still need your review — treat them as a head start, not a finished answer.

Common scenario #

A DJ replaces or reconnects a drive, and suddenly hundreds of database entries show as missing — even though the music is all still there, just at a different path.

Related pages #

• CrossRef
• Understanding the Workbook
• Typical First Repair Flow