Difference between revisions of "IMSMA Staging Area"
| Line 3: | Line 3: | ||
While in the operational {{IMSMANG}} database the item data (e.g. the ID, status and name of a Land) is stored in one table and other information about the Land (such as multi-select and custom defined fields) are stored in separate tables. Furthermore in the {{IMSMANG}} information are also stored with enumeration values and as links between objects. In the staging area all this information is flattened in one single table for each item. Therefore, there is lesser need to write complex queries to retrieve attributes of an object. | While in the operational {{IMSMANG}} database the item data (e.g. the ID, status and name of a Land) is stored in one table and other information about the Land (such as multi-select and custom defined fields) are stored in separate tables. Furthermore in the {{IMSMANG}} information are also stored with enumeration values and as links between objects. In the staging area all this information is flattened in one single table for each item. Therefore, there is lesser need to write complex queries to retrieve attributes of an object. | ||
| − | A staging area can be created out of an {{IMSMANG}} v 6.0 (and higher) database. It is typically used as a '''reporting database''', via | + | A staging area can be created out of an {{IMSMANG}} v 6.0 (and higher) database. It is typically used as a '''reporting database''', via [[MINT]] or any other [[External Reporting Tools|reporting/analysis tool]] such as Excel or ArcGIS. |
{{NavBox Business Intelligence}} | {{NavBox Business Intelligence}} | ||
[[Category:VIE]] | [[Category:VIE]] | ||
Revision as of 13:21, 10 January 2017
The IMSMA staging area is a flattened and read-only version of the IMSMANG operational database. In terms of content, the data is an exact copy of the approved information in the IMSMANG database, but the structure is less complex and therefore easier to query.
While in the operational IMSMANG database the item data (e.g. the ID, status and name of a Land) is stored in one table and other information about the Land (such as multi-select and custom defined fields) are stored in separate tables. Furthermore in the IMSMANG information are also stored with enumeration values and as links between objects. In the staging area all this information is flattened in one single table for each item. Therefore, there is lesser need to write complex queries to retrieve attributes of an object.
A staging area can be created out of an IMSMANG v 6.0 (and higher) database. It is typically used as a reporting database, via MINT or any other reporting/analysis tool such as Excel or ArcGIS.
| ||||||||||||||
