Understand what information meter proving stores in the Historical database
- Last UpdatedApr 24, 2025
- 1 minute read
There are two Historical database tables used to support the Meter Proving application.
ProverTicket
The Prover Ticket table stores the ticket information for the meter prover.
|
Field Name |
Data Type |
Description |
|---|---|---|
|
updateTime |
int(4) |
Approximate time the data was modified. |
|
proverName |
char(15) |
Unique key for a row. |
|
ticketNumber |
int(4) |
The number of the ticket. |
|
proveDate |
char(25) |
The date reported by the prover. |
|
xfr_status |
tinyint(1) |
The status of the transfer. |
RunData
All proving results are stored in the Historical database after a prove is accepted. The exceptions to this are pending prove reports that are removed from the pending reports queue for remote meter proves due to overflow conditions. Each run of a meter prove is stored in its own record in the rundata table.
|
Field Name |
Data Type |
Description |
|
updateTime |
int(4) |
Approximate time that the data was modified. |
|
provername |
char(15) |
Unique row key. |
|
ticketNumber |
int(4) |
Provides the ticket number information. |
|
runNumber |
int(4) |
Provides the run number information. |
|
xfr_status |
tinyint(1) |
Provides the transfer status information. |