Skip to main content
Skip table of contents

Requirements

Operating System

DATPROF Privacy requires:
  • Microsoft Windows 7 or higher or Microsoft Windows server 2012 or higher.

  • .NET Framework 4.8

  • The user installing the software should have the permission to install software. 

Hardware

  • CPU: x86 1GHZ or higher. 

  • Memory:  at least 4GB RAM.

  • Diskspace: at least 1GB.

Supported Databases

DATPROF adheres to the software lifecycle of the database vendors.

Oracle

Version 11.2 and above

Microsoft SQL Server

Version 2008 (not for Runtime)

Version 2012

Version 2014

Version 2016*

Version 2017*

Version 2019*

Version 2022 and above*

DB2 LUW

10.5 and above

DB2 for i

7.2

7.3

7.4

DB2 for z/OS

13.0 and above

PostgreSQL

9.5 and above

MySQL

8.0

MariaDB

10.4

Azure SQL

Not applicable - SaaS solution.

*Check the Powershell module remarks

Oracle RDBMS

Permissions and Roles

If the Privacy User is the TABLE_OWNER

Minimum System Privileges

  • CREATE SESSION

  • CREATE TABLE

Minimum Object privileges

  • EXECUTE permission on dbms_random package

  • EXECUTE permission on dbms_metadata package

Quota

  • Unlimited tablespace

If the Privacy User is not the same as the TABLE_OWNER these additional permissions are required:

  • SELECT on the tables to mask

  • REFERENCES on the tables to mask

  • ALTER on the tables to mask

  • CREATE ANY INDEX

  • DROP ANY INDEX

  • CREATE ANY TABLE

  • INSERT ANY TABLE

  • SELECT_CATALOG_ROLE

(info) When you have created your own procedure(s)/function(s), use sequences or reference views in your scripts, you should take care to grant the Privacy user the right permissions.

Microsoft Sql Server

Permissions

The user masking the database should have dbo permissions in the database targeted for data masking.

Powershell module dependency

To retrieve DDL information from Microsoft SQL Server, Datprof Runtime uses a PowerShell module. 

In time Microsoft has replaced the original "SQLPS" module by the "SqlServer" module.

As of version 4.0 the SqlServer module is delivered with Privacy and does not need to be installed manually.

For this, Microsoft PowerShell version 5 or higher is required.

Linux systems

When using Runtime on a Linux system, PowerShell must be installed and also the "SqlServer" module needs to be installed manually.

For installing PowerShell on a Linux system see the Microsoft documentation: https://docs.microsoft.com/nl-nl/powershell/scripting/install/installing-powershell-core-on-linux .

To install the required Sqlserver module execute this:

  • Open a PowerShell window on your system, either as the user running Runtime or as root

  • Install the module with the command: Install-Module -Name SqlServer

DB2 LUW 

Requirements

To use DATPROF Privacy for Linux, Unix, Windows (LUW) the following IBM software is required on the client PC: IBM DB2 Data server driver package.

After installation DATPROF Privacy will use the 32bit dll’s in the subfolders netf40 or netf40_32.

Permissions

The user masking the database should have connect, dataaccess, createtab  permissions in the database targeted for data masking.

DB2 iSeries

Requirements

You should have the IBM i Access for Windows 7.1 or IBM i Access Client Solutions installed. This software is available on the IBM site.

Permissions

The user masking the database should have DBADM  permissions in the database schema targeted for data masking.

DB2 for z/OS (Mainframe)

Requirements

In order to use Subset with DB2 for z/OS databases, the user must possess their own db2jcc_license_cisuz.jar file - This is the IBM Data Server for JDBC and SQLJ license file that allows access to the database through the JDBC protocol. This is a separate license that must be acquired through IBM. This file must then be placed in the Drivers sub-folder of the Privacy installation folder. If this is not done, the user is greeted by the following error upon trying to test a connection to the database:

Permissions

The user masking the database requires admin level permissions in the database.

Azure SQL

Permissions

The user masking the database should have admin level permissions in the database targeted for data masking.

PostgreSQL, MySQL and MariaDB

Permissions

You should at least have select permissions on the tables to import.

To execute a scenario database owner permissions are required.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.