This topic describes the high-level process for adding SAP ASE environments, linking SAP ASE databases to the Delphix Engine, and provisioning virtual databases.

Block Diagram of Linking Architecture between SAP ASE Environments and the Delphix Engine

Environment Setup

SAP ASE dSources are backed by a staging database that runs on a target host, as shown in the diagram. There is no requirement for additional local storage on this host, as the storage is mounted over NFS from the Delphix EngineAt Delphix, we refer to the creation and maintenance of this staging database on the staging host as "validated sync," because it prepares the dSource data on the Delphix Engine for provisioning VDBs later on. After the Delphix Engine creates the staging database, it continuously monitors the source database for new transaction log dumps. When it detects a new transaction log dump, it loads that dump to the staging database. The result is a TimeFlow with consistent points from which you can provision a virtual database (VDB), and a faster provisioning process, because there is no need for any database recovery during provisioning.

When you later provision a VDB, you can specify any environment as a target, including the environment that contains the staging database. However, for best performance, Delphix recommends that you choose a different target environment. The target must have an operating system that is compatible with the one running on the validated host, as described in Requirements for SAP ASE Target Hosts and Databases.

Workflow and Tasks for SAP ASE Environments

  1. Add the desired source environments as described in Managing SAP ASE Environments.
  2. Add the desired target environments as described in Managing SAP ASE Environments.
  3. Link the source database as described in Linking an SAP ASE Data Source.
  4. Provision VDBs as described in Provisioning an SAP ASE VDB.

Best Practice

If possible, it is recommended to use separate ASE instances for staging databases (dSources) and VDBs on target environments. This allows better control on target environments based on the resources required for ASE full/transaction log dump ingestion vs VDB performance.

Related Links