Tracking Changes - Mastering phpMyAdmin 3.4 for Effective MySQL Management - page 305

Configuring a basic tracking mechanism
In config.inc.php , for a specific MySQL server's configuration, the
$cfg['Servers'][$i]['tracking'] should contain the name of the tracking table;
the suggested name is pma_tracking to match the default value inside scripts/
create_tables.sql .
If this directive is left blank, no tracking is possible on this
server (we won't see any Tracking menu).
By default, tracking must be activated per table. If we prefer that the tracking
mechanism be switched on automatically for all future tables and views, the
$cfg['Servers'][$i]['tracking_version_auto_create'] can be set to TRUE .
Please note that this is only for future tables and views—we still need to activate
tracking for existing tables.
The advantage of using automatic creation is that we don't have to think about it;
tracking is done from the birth of a table. An inconvenient side effect of this is that
we don't have the possibility of choosing which statements will be tracked; these will
be taken from the default list (refer to the Choosing the statements to be tracked section
later in this chapter).
Other configuration directives will be discussed in the section that relates to them.
Principles
This section defines important principles on which the tracking mechanism is based:
versioning, snapshot, and the archiving issues of tracking information.
Versioning
Using version numbers is something we are familiar with; for example, this topic
describes phpMyAdmin version 3.4.x. However, at this point we must understand
exactly why we use version numbers.
A good reference on software versioning is located in Wikipedia at
http://en.wikipedia.org/wiki/Sof tware_versioning . This article mentions
that version names can be used, but version numbers are more common. More
importantly, it states that version numbers "correspond to new developments in
the software".