Create the database for External Data Mart

Last Updated : Jul 08, 2022 |

External Data Mart (EDM) is a feature of Context Store that enables persistence of context information from the in-memory data-grid to an external database. This feature is mandatory for an Avaya Oceana® deployment. It stores the data required to build Customer Journey View in Avaya Workspaces.

You must create the required schema in the Context Store-supported database type and configure EDM through the External Data Mart Configuration group in OceanaConfigurationService.

For more information on supported databases, see Deploy External Data Mart overview

All existing users must migrate to one of the supported versions of Microsoft SQL Server 2016. For procedures to migrate from Oracle or PostgreSQL to MS SQL Server, see the Upgrading Avaya Oceana® document.

Avaya Oceana® Release 3.8 and higher supports the following installation options for EDM:

  • EDM and Avaya Control Manager co-resident on the same Microsoft SQL server.

    • For new Avaya Oceana® deployments, see the Deploy External Data Mart on Avaya Control Manager SQL Server section in this document.

    • For upgrading to install EDM co-resident with the Avaya Control Manager on the same MS SQL server, see the relevant chapter in the Upgrading Avaya Oceana® document.

  • EDM standalone installation on MS SQL.

    • For information on how to install an EDM database and create tables, see the Deploy External Data Mart on standalone SQL Server section in this document.

Important:

  • In an Avaya Oceana® deployment, EDM is a mandatory requirement.

  • You must monitor and maintain the EDM database to ensure that it does not consume unnecessary space. Keep purging old or unused data from the EDM database at regular intervals. Take a backup of the EDM database before undertaking any maintenance activity.

Note:

When installing SQL Server on virtual machines, Avaya recommends reading VMware's best practices published at https://www.vmware.com/content/dam/digitalmarketing/vmware/en/pdf/solutions/sql-server-on-vmware-best-practices-guide.pdf. A summary of these recommendations includes:

  • Store database Log files and database Data files on separate disks. This avoids I/O contention and improves performance.

  • Install SQL Server and the Windows operating system on the same disk.