Bert Swope
Databases & Schemas
This is a snippet of very useful information, which is buried in the IBM documentation. So, I thought I would bring it up a level for those of you who may be making decisions regarding Information server installations (IIS). The table below provides an excerpt of the IBM IIS repository databases placement and guidance. Please, keep in mind that which of these databases may be required for your installation may be a subset of these database depending upon your IIS product offering license.
Metadata Repository Databases
Repository or Database |
Description |
Default Database And Schema |
|
Active Infosphere Information Server Metadata Repository | Stores the metadata about external data sources that are governed, managed, and analyzed by InfoSphere Information Server components. Normally referred to as the metadata repository. | Database: XMETA
Schema: XMETA Database must be the same database that is used for the staging metadata repository. |
| Infosphere Information Server Staging Area | Stores metadata that is imported from external data sources so that it can be examined before it is moved to the active metadata repository. | Database: XMETA
Schema: XMETASR Database must be the same database that is used for the active metadata repository. |
| Analysis Database | Stores results of information analysis by InfoSphere Information Analyzer. | Database: IADB
Schema: IAUSER Database cannot be the same database that is used for the active metadata repository or staging area. |
| Operations Database | Stores monitoring data that is displayed by the InfoSphere DataStage® and QualityStage®Operations Console. | Database: XMETA
Schema: User-defined repository user name, typically DSODB Database can be the same or different as the database that is used for the metadata repository. |
| Standardization Rules Designer Database | Stores a copy of revisions to InfoSphere QualityStage rule sets that have been made in the IBM InfoSphere QualityStage Standardization Rules Designer. | Database: XMETA
Schema: User-defined data store user name, typically SRDUSER Database can be the same or different as the database that is used for the metadata repository. |
| Exceptions Database | Stores exceptions that are generated by InfoSphere Information Server products and components. | Database: XMETA
Schema: User-defined repository user name, typically ESDB Database can be the same or different as the database that is used for the metadata repository. |
| Match Designer Database | Stores the results of match test passes by InfoSphere QualityStage Match Designer, a component of InfoSphere QualityStage. This data store is an ODBC data source that is used as a staging area before match designs are checked in to the active metadata repository. |
Database: MDDB User-defined database name and schema name. No default, but typically MDDB. Database cannot be the same database as that used for the metadata repository. |
analytics, #DataIntegration,#informationserver,#Informationtechnology, #IT,Component,
1 Comment