Understand the Ticket Hourly Integration (TicketHourlyIntegration) table
- Last UpdatedApr 24, 2025
- 1 minute read
The Ticket Hourly Integration (ticketHourlyIntegration) table contains Historical information related to the amount of volume that was processed by a batch transfer (batchXfer) record for a specific length of time and the ticket that was currently active. Each start, stop, and split of the ticket creates a new row in the table.
The hourly sum of integrated volume can be gathered through a query of the batchHourlyIntegration view. The batchHourlyIntegration view presents a subset of the columns contained in the ticketHourlyIntegration table. The batchHourlyIntegration view will aggregate all entries in the table for each batch and associated batch transfer for every hour. At this point, the GSV_intg value is summed.
Views, unlike tables, cannot be edited. However, they can be queried in a manner similar to tables.
The following table shows the fields in the ticketHourlyIntegration table:
|
Internal Field |
Data Type |
Description |
|---|---|---|
|
msrepl_tran_version |
Uniqueidentifier |
Unique record identifier. |
|
time |
GMTtime(int) |
The time that the entry was created within the Historical database. |
|
time_period_start |
GMTtime(int) |
The hour that the integration volume belongs to. |
|
offset |
GMToffset(smallint) |
The timezone that the time and time_period_start column values are made in. |
|
ticket_no |
Varchar(15) |
The ticket that the integration volume belongs to. |
|
batchXfer |
nameType(varchar32) |
The name of the batchXfer record that the integration volume belongs to. |
|
batchID |
nameType(varchar32) |
The name of the batch that the integration volume belongs to. |
|
GSV_Intg |
float |
The integration volume amount. |
|
volUnit |
Varchar(15) |
The volume unit that the integration volume is in. |
|
ownsysID |
tagIDType |
The system ID that made the integration entry. |
|
datasetID |
tagIDType |
The dataset ID that the entry belongs to. |