Previous PDF

swipe to navigate


Hitachi ID Identity and Access Management Suite requires a database server -- to store configuration data, user profile data, security policies, workflow requests and more. Installing an appropriate database server is pre-requisite to installing and configuring Hitachi ID Suite.

This document offers guidance regarding selection, placement and configuration of the database server software used as a "back end" for Hitachi ID Suite.

Choosing a database product

The first and most obvious question when considering the database architecture for Hitachi ID Suite is which database software is supported?

The Hitachi ID Suite replicating data service can be configured to use the following SQL database engines as its physical data store:

  • Microsoft SQL Server 2016/2014/2012, Standard Edition.
  • Microsoft SQL Server 2016/2014/2012, Express Edition, with Advanced Services (free download from -- suitable for development, test and very small production environments.

These options are all technically compatible, but which is most appropriate for a given deployment? That depends on how Hitachi ID Suite will be used, as follows:

Demonstration or proof of concept

If Hitachi ID Suite is being installed in a demonstration setting, for example to evaluate its suitability for a given business problem, then cost is likely a dominant consideration. In this case, Microsoft SQL Server Express is appropriate, as it is offered at no cost:

Production deployments

In a production deployment of Hitachi ID Suite, the no-cost SQL Express is not appropriate:

  1. It has strict limitations on data volume (10GB).
  2. There are severe performance governors -- a single CPU core and 1GB of RAM.
  3. There is no technical support.

This means that the "Standard" or "Enterprise" version of SQL Server should be used, rather than the "Express" edition:

Previous Next PDF