Script History
Browsing how the scripts in a database changed over time.
Alongside recording execution, fmTrace keeps a history of the scripts themselves. Every time it sees a database, it notes what changed in the script text since the last time — so you can look back at how a script got to be the way it is.
Opening it
The Tracking tab carries a Script History link for whichever database is currently active. Clicking it opens the history window on that database.
What you see
A history window over the scripts in one database: which scripts changed, when, and what the change was — the script text before and after, side by side.
What it is good for
- Working out when a script picked up the step that is now costing you eleven seconds — pair it with a recording that shows the cost.
- Recovering a version of a script you overwrote.
- Seeing what a colleague changed in a shared file.
History accumulates as you work.
The history is built from what fmTrace observes. A database it has never seen has no history yet, and the record starts from the first time it does see it.