Database Mapper System Requirements

MySQL versions 5.6 through 8

Oracle versions 12c Release 1 through 21c

PostgreSQL versions 9.5 through 13.2

Note:  Microsoft SQL Server Transact-SQL ScriptDom is included in the Database Mapper installer.

Important:  The SQL Server provider works against SQL Server 2005 and above when connecting to both SQL Server On-Premises and Azure Instances. The SQL Server Provider can collect columns with the Sensitivity Classification in Azure, and SQL Server 2019.

Important:  The SSAS provider works against SSAS 2005 and above when connecting to Multidimensional Instances and SSAS 2012 and above when connecting to a Tabular Instances.

SQL Server Integration Services 2012 or later

• SQL Server Reporting Services (2012 or later)
• Support provided for the following report locations:
  • File System: SQL Server 2012 or later
  • Native Web Services: SQL Server 2012 or later
  • SharePoint Web Service: SQL Server 2012 or later

Note: 

• These requirements are for Power BI Report Server. Power BI itself does not have any additional requirements beyond what is required for Database Mapper.
• KPIs and Mobile Reports are currently not supported when connecting to an SSRS 2016 or above Report Server.

You need to install Microsoft ® .NET 4.5 to monitor SSAS 2017.

To connect to Azure Analysis Services, you need to download and install the latest Microsoft Analysis Services Client Libraries.

Note:  You need to select SQL Server Integration Services when installing SQL Server features in Microsoft SQL Server Data Tools.

You need to have any Third-Party Products (Connection Managers, Tasks, Components, etc) that are used within the SSIS Package(s) installed to document your packages.

Note:  You need to select SQL Server Reporting Services when installing SQL Server features in Microsoft SQL Server Data Tools.

• Content.Create
  • Delegated
  • Create content
• Dashboard.Read.All
  • Delegated
  •  View all dashboards
• Dashboard.ReadWrite.All
  • Delegated
  • Read and write all dashboards
• Dataset.ReadWrite.All
  • Delegated
  • Read and write all datasets
• Group.Read
  • Delegated
  • View user's groups
• Report.ReadWrite.All
  • Delegated
  • Read and write all reports

• Requires SELECT permission on mysql.user.
• Permissions on any tables that will be documented.
• For triggers to be included, the TRIGGER privilege is required.
• For the definitions of stored procedures and functions to be included in the documentation, user must be named in the DEFINER clause for the object; or for MySQL prior to version 8, user needs SELECT permission on mysql.proc, or for MySQL version 8 (or later), user needs SHOW_ROUTINE privilege.
  • Note:  If permissions for these are not in effect, but the user has a permission (SELECT, INSERT etc.) on the object, then that object will be in the documentation but the definition section will be missing.

Examples

Setting permissions on a limited user account (to enable configuring a solution item and taking a snapshot):

GRANT SELECT ON mysql.user TO 'MyUserName'@'%';
GRANT SELECT, TRIGGER ON myschema.* TO 'MyUserName'@'%'; -- ALL tables/views

For stored procedures or functions:

 MySQL prior to version 8:

GRANT SELECT ON mysql.proc TO 'MyUserName'@'%';

MySQL version 8 (or later):

GRANT SHOW_ROUTINE ON *.* TO 'lockdownuser'@'%';

• Permissions are required to connect to the database.
• Permissions are required to access any objects that will be documented.
• For triggers to be documented, the CREATE ANY TRIGGER privilege is required.

• Requires LOGIN privilege
• Requires CONNECT privilege to the database
• Requires permissions on any objects you want to document. 
  • Note:  For triggers to be included, extra privileges on the table other than SELECT alone are required (e.g. INSERT)

Example

Setting permissions on a limited user account (to enable configuring a solution item and taking a snapshot):

ALTER ROLE myusername WITH LOGIN;
					
GRANT CONNECT ON DATABASE mydatabase TO myusername;
				
GRANT SELECT, INSERT ON ALL TABLES IN SCHEMA myschema TO myusername;

• Definition permissions for any object you want to document
• Non-sysadmin users must be granted View Server State permissions to view log file objects within the documentation.

• Multidimensional:
  • Read definition permission on each database object you want to document
• Tabular:
  • Administrator permission on each database object you want to document
• Azure Analysis Services
  • Azure Active Directory credentials are required

• SSIS Catalog:
  • Read and Modify permission for each project within the SSISDB you want to analyze

• Folder Security Settings:
  • Minimum Predefined User Roles required:
    • My Reports
    • Content Manager
  • Minimum Tasks required for a custom User Role:
    • View Reports
    • View Folders
    • View Data Sources
    • View Models
    • Consume Reports
• Web Service Security Settings:
  • Minimum Predefined System Role required:
    • System User
    • Browser in the report tree
  • Minimum Tasks required for a custom System Role:
    • Execute Report Definitions

• You must be a part of the Server Administrator role