Database
This section identifies hardware and software requirements for Identity Manager's database.
Hardware
Database disk storage requirements depend on the database lifespan and number of entries. For example, 100,000 users typically require approximately 10 GB of storage.
The maximum SQL Express database is 10 GB.
Software
Identity Manager uses a SQL Server database and supports SQL Server 2016 or later.
The database requirements may depend on the chosen SQL Server edition and version.
Recommended features
Netwrix also highly recommends the following features:
-
Always On availability groups: only available in the Enterprise edition of SQL Server 2016 or later
FAQ: How to enable Always On availability groups in SQL Server?
-
Database Mirroring: available in all editions of SQL Server 2016 or later
The data history feature introduced in Identity Manager v5.1.0 might cause some tables to grow significantly.
Enabling the Table Partitioning feature for the UR_Resource and UP_Assigned* tables greatly improves database performance:
UP_Assigned* Tables |
|---|
| UP_AssignedResourceTypes |
| UP_AssignedSingleRoles |
| UP_AssignedCompositeRoles |
| UP_AssignedNavigationRules |
| UP_AssignedScalarRules |
This feature is available and enabled by default in SQL Server 2016 or later.
Additional tools
Installing and setting up the database requires either SQL Server Management Studio or the sqlcmd command line tool.
SQL Server Authentication
Identity Manager can authenticate to SQL Server using either a SQL Server authentication login or a Windows authentication login.
Netwrix recommends using Windows authentication to log in to the SQL Server and avoid storing a plain text password in the technical configuration files.
SQL Server Roles
The database administrator must be able to assign the following roles to the service account used by Identity Manager to access the SQL Server database:
db_ownerwhich is a database-level role. This role grants its owner the authorization to perform all configuration and maintenance activities on the database, and to drop the database in SQL Server.bulkadminwhich is a server-level role. This role grants its owner the authorization to perform bulk operations on the database.
Although bulkadmin is a server-level role, it still requires Identity Manager to have database-level permissions granted by the db_owner role. Bulk operations can run on the database only if Identity Manager has the db_owner role.
Granting bulkadmin role to the server's service account requires access to an account member of the sysadmin or securityadmin server-level role on the target SQL Server. See the Install the Server topic for additional information.
For more information about identity and permission management in SQL Server, see Microsoft's documentation.
Shared SQL Server and Dedicated Database
Use Identity Manager's SQL Server installation to host other database applications.
Identity Manager's database itself must serve Identity Manager exclusively.
Connection to the Server
SQL feed must be open from Identity Manager's server to SQL Server.
Optimization
Set the max degree of parallelism (MAXDOP) to 1 in the SQL database.
What's Next
Next, review the requirements for Identity Manager's server. See the Server topic for additional information.