Table of Contents

Search

  1. Preface
  2. Summary of PowerExchange New Features and Changes
  3. PowerExchange Installation and Upgrade
  4. PowerExchange Agent
  5. PowerExchange Client for PowerCenter
  6. PowerExchange Condense
  7. PowerExchange Listener
  8. PowerExchange Logger for Linux, UNIX, and Windows
  9. PowerExchange Navigator
  10. PowerExchange Monitoring and Tuning
  11. PowerExchange Utilities
  12. PowerExchange for Adabas
  13. PowerExchange for CA Datacom
  14. PowerExchange for DB2 for i
  15. PowerExchange for DB2 for Linux, UNIX, and Windows
  16. PowerExchange for DB2 for z/OS
  17. PowerExchange for CA IDMS
  18. PowerExchange for IMS
  19. PowerExchange for Microsoft SQL Server
  20. PowerExchange for MySQL
  21. PowerExchange for Oracle
  22. PowerExchange for PostgreSQL
  23. PowerExchange for VSAM and Flat Files
  24. PowerExchange ODBC

Support for SQL Server Always On Availability Groups

Support for SQL Server Always On Availability Groups

PowerExchange 10.1.1 can capture changes that are written to an availability database in a SQL Server Always On Availability Group. An Availability Group consists of primary and secondary replica databases on multiple nodes in a Windows Server Failover Clustering (WSFC) cluster. Only the following configuration has been tested and certified for PowerExchange CDC:
  • The distribution database is installed on a node outside of the Always On Availability Group cluster, which is consistent with SQL Server requirements.
  • PowerExchange is installed on a node outside of the Always On Availability Group cluster.
  • When you create a registration group for the SQL Server Always On Availability Group source, you specify the Availability Group listener name in the
    Database Server
    field.
If you need to use another configuration, contact Informatica Global Customer Support. Informatica will try to accommodate your request.
After CDC processing is running, If the primary database fails over to a secondary replica database on another node, PowerExchange can continue to capture change data from the distribution database without data loss.

0 COMMENTS

We’d like to hear from you!