Meta Integration® Model Bridge (MIMB)
"Metadata Integration" Solution

MIMB Bridge Documentation

MIMB Import Bridge from SAS Base SAS Code

Bridge Specifications

Vendor SAS
Tool Name Base SAS Code
Tool Version 9x
Tool Web Site http://support.sas.com/documentation/cdl/en/lrcon/65287/HTML/default/viewer.htm
Supported Methodology [Data Integration] Multi-Model, Data Store (Physical Data Model), (Source and Target Data Stores, Transformation Lineage, Expression Parsing, Expression Conversion) via SAS TXT File

Import tool: SAS Base SAS Code 9x (http://support.sas.com/documentation/cdl/en/lrcon/65287/HTML/default/viewer.htm)
Import interface: [Data Integration] Multi-Model, Data Store (Physical Data Model), (Source and Target Data Stores, Transformation Lineage, Expression Parsing, Expression Conversion) via SAS TXT File from SAS Base SAS Code
Import bridge: 'SqlScriptSas' 10.0.1

The purpose of this SAS code import bridge is to detect and parse all its embedded SQL statements in order to generate the scope (data models) of the involved source and target data stores, as well as the data flow lineage and impact analysis (data integration ETL/ELT model) between them.
The import proces consists of multiple stages including SAS code interpretation that allows to extract and prepare the SQL statements for further analysis. In SAS code, the SQL queries are located inside procedure called 'PROC SQL'. The interpreter also helps to convert SAS specific expressions into the generic structures that can be recognized by the SQL parser.
The bridge allows to replace SAS variables (e.g. &var.) in SQL queries using a separate file that contains all the necessary values. For more details please refer to documentation for bridge parameter 'Miscellaneous' and the section for key '-s'.


Bridge Parameters

Parameter Name Description Type Values Default Scope
Directory Select a directory with the textual files that contain SAS code to import. DIRECTORY     Mandatory
Directory Filter Specify a search filter for the sub directories. Use regular expressions in java format if needed (e.g. '.*_script'). Multiple conditions can be defined by using a space as a separator (e.g. 'directory1 directory2'). The condition must be escaped with double quotes if it contains any spaces inside (e.g. "my directory"). Negation can be defined with the preceeding dash character (e.g. '-ddl'). STRING      
File Filter Specify a search filter for files. Use regular expressions in java format if needed (e.g. '.*\.sql'). Multiple conditions can be defined by using a space as a separator (e.g. 'file1 file2'). The condition must be escaped with double quotes if it contains any spaces inside (e.g. "my file.sql"). Negation can be defined with the preceeding dash character (e.g. '-\.tar\.gz'). STRING      
Miscellaneous Specify miscellaneous options identified with a -letter and value.

For example, -s c:\values.txt -e UTF-16 -d schema

-s: path to a file that resolves Shell parameters in either Windows (%param%) or in Linux (${param}, $1) format. This parameter can be used to define a path to the key/value pair file. The path can be escaped with double quotes if it contains spaces or any special characters. The records from the file will be used to preprocess all the scripts and replace the corresponding Shell parameters with the actual values. The key literals must not be decorated with the escape characters and the matching rules are case sensitive. Character colon ':' is used as a key/value pair delimiter and must be escaped with backward slash '\' if it is part of the parameter name. For example, for script 'INSERT INTO %SCHEMA1%.t1(c1) SELECT a from %SCHEMA2%.t2;' the file with the parameters can be organized in the following way:
SCHEMA1:actual_schema1
SCHEMA2:actual_schema2
-d: default schema. Allows to specify a schema name for the objects that don't have it defined explicitly.
-e: encoding. This value will be used to load text from the specified script files. By default, UTF-8 will be used. Here are some other possible values: UTF-16, UTF-16BE, US-ASCII.
STRING      

 

Bridge Mapping

Mapping information is not available

Last updated on Fri, 21 Sep 2018 16:15:06

Copyright © Meta Integration Technology, Inc. 1997-2018 All Rights Reserved.

Meta Integration® is a registered trademark of Meta Integration Technology, Inc.
All other trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.