Microsoft Access Connector | Collate Database Integration Guide

• Connection: Choose the source location for your Access database files. Two options are supported:
  • Local File Path: Provide the absolute path to a single .accdb or .mdb file, or a directory containing Access database files. Supports ~ expansion (e.g. ~/data/sales.accdb). When pointing to a directory, all .accdb and .mdb files found recursively will be ingested as separate databases.
  • S3 Connection: Connect to Access database files stored in an Amazon S3 bucket (or S3-compatible storage such as MinIO). Configure the following fields:
    • AWS Access Key ID & AWS Secret Access Key: AWS security credentials to authenticate requests. Access keys consist of two parts: an access key ID (for example, AKIAIOSFODNN7EXAMPLE) and a secret access key. You must use both together to authenticate. Find more information on how to manage your access keys here.
    • AWS Region: The AWS region where your S3 bucket is located (for example, us-east-1). This is the only required parameter when configuring an S3 connection. Find further information about configuring credentials here.
    • AWS Session Token (optional): Required when using temporary credentials. Find more information on Using temporary credentials with AWS resources.
    • Endpoint URL (optional): Use a custom endpoint for S3-compatible storage services (for example, http://localhost:9000 for MinIO). Find more information on AWS service endpoints.
    • Profile Name (optional): A named AWS CLI profile to use instead of default. Find more information about Named profiles for the AWS CLI.
    • Assume Role ARN (optional): The ARN of an IAM role to assume for cross-account access. Find more information on AssumeRole.
    When using Assume Role authentication, ensure you provide the following details:

    • AWS Region: Specify the AWS region for your deployment.
    • Assume Role Session Name (optional): An identifier for the assumed role session. Defaults to CollateSession.
    • Assume Role Source Identity (optional): The source identity for the AssumeRole operation, used for auditing in AWS CloudTrail.
    • Bucket Names: The S3 bucket name containing the Access database files to ingest. Only the first bucket in the list is used per pipeline run.
• Table Filter Pattern (optional): Regex pattern to include or exclude specific tables during ingestion. When left blank, all tables are ingested.

• Connection Options (Optional): Enter the details for any additional connection options that can be sent to database during the connection. These details must be added as Key-Value pairs.
• Connection Arguments (Optional): Enter the details for any additional connection arguments such as security or protocol configs that can be sent during the connection. These details must be added as Key-Value pairs.

​

Metadata Ingestion Options

• Name: This field refers to the name of ingestion pipeline, you can customize the name or use the generated name.
• Database Filter Pattern (Optional): Use to database filter patterns to control whether or not to include database as part of metadata ingestion.
  • Include: Explicitly include databases by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all databases with names matching one or more of the supplied regular expressions. All other databases will be excluded.
  • Exclude: Explicitly exclude databases by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all databases with names matching one or more of the supplied regular expressions. All other databases will be included.
• Schema Filter Pattern (Optional): Use to schema filter patterns to control whether to include schemas as part of metadata ingestion.
  • Include: Explicitly include schemas by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all schemas with names matching one or more of the supplied regular expressions. All other schemas will be excluded.
  • Exclude: Explicitly exclude schemas by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all schemas with names matching one or more of the supplied regular expressions. All other schemas will be included.
• Table Filter Pattern (Optional): Use to table filter patterns to control whether to include tables as part of metadata ingestion.
  • Include: Explicitly include tables by adding a list of comma-separated regular expressions to the Include field. OpenMetadata will include all tables with names matching one or more of the supplied regular expressions. All other tables will be excluded.
  • Exclude: Explicitly exclude tables by adding a list of comma-separated regular expressions to the Exclude field. OpenMetadata will exclude all tables with names matching one or more of the supplied regular expressions. All other tables will be included.
• Enable Debug Log (toggle): Set the Enable Debug Log toggle to set the default log level to debug.
• Mark Deleted Tables (toggle): Set the Mark Deleted Tables toggle to flag tables as soft-deleted if they are not present anymore in the source system.
• Mark Deleted Tables from Filter Only (toggle): Set the Mark Deleted Tables from Filter Only toggle to flag tables as soft-deleted if they are not present anymore within the filtered schema or database only. This flag is useful when you have more than one ingestion pipelines. For example if you have a schema
• includeTables (toggle): Optional configuration to turn off fetching metadata for tables.
• includeViews (toggle): Set the Include views toggle to control whether to include views as part of metadata ingestion.
• includeTags (toggle): Set the ‘Include Tags’ toggle to control whether to include tags as part of metadata ingestion.
• includeOwners (toggle): Set the ‘Include Owners’ toggle to control whether to include owners to the ingested entity if the owner email matches with a user stored in the OM server as part of metadata ingestion. If the ingested entity already exists and has an owner, the owner will not be overwritten.
• includeStoredProcedures (toggle): Optional configuration to toggle the Stored Procedures ingestion.
• includeDDL (toggle): Optional configuration to toggle the DDL Statements ingestion.
• queryLogDuration (Optional): Configuration to tune how far we want to look back in query logs to process Stored Procedures results.
• queryParsingTimeoutLimit (Optional): Configuration to set the timeout for parsing the query in seconds.
• useFqnForFiltering (toggle): Regex will be applied on fully qualified name (e.g service_name.db_name.schema_name.table_name) instead of raw name (e.g. table_name).
• Incremental (Beta): Use Incremental Metadata Extraction after the first execution. This is done by getting the changed tables instead of all of them. Only Available for BigQuery, Redshift and Snowflake
  • Enabled: If True, enables Metadata Extraction to be Incremental.
  • lookback Days: Number of days to search back for a successful pipeline run. The timestamp of the last found successful pipeline run will be used as a base to search for updated entities.
  • Safety Margin Days: Number of days to add to the last successful pipeline run timestamp to search for updated entities.
• Threads (Beta): Use a Multithread approach for Metadata Extraction. You can define here the number of threads you would like to run concurrently.