Transactional Replication Support in Identity Manager

Products

• CA Identity Manager
• CA Identity Suite

Issue/Introduction

Broadcom Identity Manager does not support Transactional Replication for its database. This article explains the technical reason for this limitation and provides recommendations for alternative database replication methods.

Environment

Identity Manager 14.x

Cause

Transactional replication requires a primary key constraint on every published table. Identity Manager includes several internal tables that do not have primary keys, which makes them incompatible with this replication type.

Resolution

If you require database replication, consider the following alternatives:

• Merge Replication: Does not require a primary key.
• Snapshot Replication: Does not require a primary key.

Recommendations

• If you choose to use Merge or Snapshot replication and your tables happen to contain primary keys, you must ensure those primary keys are included in the replication process.
• Consult your database administrator to determine whether Merge or Snapshot replication best aligns with your business requirements and performance needs.

Additional Information

For additional details on replication types and constraints, please refer to the following Microsoft documentation:

• Types of Replication
• Merge Replication
• Snapshot Replication
• Managing Constraints on Published Tables