During its work MetaMiner accesses multiple databases. Some of them are accessed indirectly via Content Management Servers which take care about RDBMS versions and structures, and some of the databases are accessed directly (see How MetaMiner fits within Your Organization).
There are three types of databases accessed directly by MetaMiner:
• | MetaMiner Database (MMDB) |
• | Audit Database(s) |
• | Supplementary database for local technical purposes (not configurable; always PostgreSQL) |
The following table shows possible database combinations and supported versions:
RDBMS |
Version |
Supported for MMDB |
Supported for Audit DB |
Notes |
||||
---|---|---|---|---|---|---|---|---|
Microsoft SQL Server |
2008 |
Express Editions are supported for evaluation purposes only. Other editions are fully supported. The Enterprise Edition is recommended. The database user specified in MetaMiner Administrator (see also Setting Up Access to MMDB) must have DBA-level access to MMDB. |
||||||
2012 |
||||||||
2014 |
||||||||
Oracle Database |
10 |
For Oracle 10, version 10.2.0+ (10gR2) is required. The database user specified in MetaMiner Administrator (see also Setting Up Access to MMDB) must be granted with the following additional permissions in MMDB (mmuser stands for this user account):
|
||||||
11 |
||||||||
12 |
In any case, the following requirements apply to a database prepared to become MMDB:
• | it must be created before installing MetaMiner, |
• | the database must be empty, have no tables, nor other objects, |
• | the database user must be granted with the following permissions in this database: DELETE, UPDATE, CREATE, INSERT, TRUNCATE permissions for the following database objects: TABLE, SESSION, VIEW, TRIGGER, SEQUENCE, STORED PROCEDURE, FUNCTION, INDEX. |
If permissions are not sufficient, MetaMiner Administrator will report it during connection validation.
There is no need to create a dedicated database user account and/or a dedicated system user account on a computer running MetaMiner Server.
See also