AMT data models
AMT reports are written off two types of database; the live, On Line Transactional Processing database used by AMT, and a data warehouse On Line Analytical Processing database. It is important that the differences between the two are understood so that anyone writing reports can decide which is appropriate for any particular reporting requirement.
Live data models tap directly into AMT’s transactional database and display the most updated information, whereas On Line Transactional Processing data models do not display live data (given that data needs to be extracted and consolidated), but they do allow customers to consolidate and query data from multiple AMT installations in a single place.
Consolidating data into an AMT data warehouse is an advanced feature used by organisations with multiple AMT installations (for example, a multinational with separate AMT installations in several different countries).
By default, the process of extracting and consolidating data occurs daily through a system task. There is some flexibility in terms of how often this task can be scheduled (depending on data volumes). Please contact your System Administrator to discuss the possibility of shortening the intervals.
Cubes vs views
While the approach to writing reports using either models or views is essentially the same, there are a few steps in the process of developing the individual datasets and filters that may differ within SQL Server’s Report Builder. These differences, wherever they occur, are highlighted in various help topics.
| OLTP | Cubes |
Availability and Scheduled Hours |
| Views |
Budgeting |
|
| OLAP | Cubes |
Work Order |