Skip to content

Configuration steps

The process of setting up a Oracle Data Intake Process involves several key actions. The different sections of the input form are organized into these main steps.

Step 1. Configure Data Intake Process

Please see on the common Sidra connector plugins section about the parameters needed to configure a Data Intake Process.

Step 2. Configure Provider

Please see on the common Sidra connector plugins section about the parameters needed to create a new Provider.

Step 3. Configure Data Source

The data source represents the connection to the source database. A Data Source abstracts the details of creating a Linked Service in Azure Data Factory.

Some key aspects to take into account in this section are:

  • The fields required are the Integration Runtime and the connection string to the database.

  • Sidra Oracle connector plugin will register this new data source in Sidra Metadata and deploy a Linked Service in Azure Data Factory with this connection.

  • The created Linked Service will use Key Vault in Sidra Core to store the connection string to the database.

  • Default value for Integration Runtime is AutoResolveIntegrationRuntime.

For more details on Linked Services check the Data Factory documentation.

The information that needs to be provided is the following:

  • Integration Runtime: this is the ADF integration runtime in charge of executing the connection between the data origin, and is associated with a deployed Linked Service. In case it is not required any IR, the option Default will be selected.
  • Connection Details:
    • Server Name.
    • Database Name.
    • Username: user with access to the database.
    • Password: user password.

Step 4. Configure Metadata Extraction

Sidra Oracle connector plugin replicates the schema and tables from the source database, by querying the SYS.all_objects Oracle System View tables.

The extracted schema is replicated to the Sidra Metadata model hierarchy. Tables in the database source system are replicated in Sidra as Entities, and columns of these tables, as Attributes.

The Entity table in Sidra metadata model contains data about the format of the Entity generated, as well as information about how this Entity should be handled by the system. Attributes contain data about the columns of the tables. Sidra adds additional system-level Attributes to convey system-handling information at the level of the Entity (or table).

As part of the metadata extraction of a Data Intake Process setup, the autogenerated transfer query / DSU ingestion will be executed following the selected configuration scenario, transforming the data in raw storage into the optimized format in the Data Lake.

For more details, please check the Data Ingestion documentation.

The metadata extraction represents in which way the origin will be consumed in order to obtain its metadata. The information fields required to fill in the Metadata extraction section will be used for three main purposes internally in Sidra:

  • Create and populate the Sidra Core metadata structures (Entities and Attributes).
  • Create, deploy and execute an Azure Data Factory pipeline for the metadata extraction steps (see below steps).
  • Auto-generate the create tables and executes the autogenerated transfer query / DSU ingestion, including all the steps for storing the optimized data in the data lake storage.

These are the metadata extractor configuration parameters to be input for this version of connector plugin. All of these parameters are optional:

  • Number of Tables per Batch: is the number of tables to be analyzed per batch by the metadata extractor pipeline. This field must be an integer value between 1 and 100. If not specified, the default value is 50.
  • Types of Objects to Load: it corresponds to the object types in the source database to include in the metadata extraction. It can be: Views, Tables or both.

  • Object Restriction Mode: there can be three options here to choose:

    • Include all objects: all objects from all databases will be imported (default value).
    • Include some objects: to specify a list of objects to include.
    • Exclude some objects: to specify a list of objects to exclude.

  • Object Restriction List: this is the list of objects (either Tables or Views) in the source database to include or exclude from the metadata extraction, depending on the Object Restriction Mode configured. It corresponds to OWNER and OBJECT_NAME fields in the SYS.all_objects Oracle System Table. If no values are specified in this field, all objects will be loaded. To fill in this field, add a list of [SID].[schema_name].[table_name] or [SID].[schema_name] or [SID] elements plain text, separated by comma. Examples: [SIDNAME].[OT].[CONTACTS], [SIDNAME].[HR], [SIDNAME].

Once the metadata extractor pipeline has been created, it is executed. This execution could take a while (from 5 to 15 minutes) depending on the load of Data Factory and the status and load of the associated Databricks cluster. Sidra exposes API endpoints as well to manually execute the SQL Metadata extractor pipeline.

Step 5. Configure Trigger

Please see on the common Sidra connector plugins section about the parameters needed to set up a trigger.