The SQL provider is part of Data Panel and requires a Data Panel license key to be used. If the Providers Type dropdown list says "SQL Connection – License Required", then the key still needs to be applied.
The SQL Provider is able to scan data into the Time Traveler from MySQL, Oracle DB, and MS Sql Server. The SQL provider uses the managed .NET library for Oracle so it is not necessary to install the Oracle client.
The SQL Provider is able to scan from multiple tables and/or queries and interpret the results as different object types.
To start configuring the SQL provider, specify a connection string and database type
Next press the "New" button to add a table strip.
Expand the table strip to configure settings. The strip must have a unique name. If a query is specified inside the strip settings the name is arbitrary. Otherwise it must the be name of the table or view to be scanned.
Next configure a unique ID for the given table/view/query. The key field must be unique and should not change over time. It is not required to have a database level constraint on it. If using a compound key separate the column names with commas. Note that like the delimited provider reference attributes are only supported with a single key field.
The object type definition defines how the Object Type property of resultant object records is defined. If the value is wrapped in square braces it will be treated as a type column name.
You may optionally specify a query to produce data instead of relying on a single table name. This is useful if joins or filtering are desired in the dataset production.
Some columns may be identified as reference fields provided they contain values matching those in the key field column.
Initial Load and Schedule
One the provider is configured and saved it will be appear in Panel Tools to run an initial load scan.
After the data is successfully scanned into Identity Panel you may configure a schedule step to perform regular refresh scans. Note that Identity Panel must iterate the entire table or view on every scan so don't schedule scans overly frequently. Daily, or every few hours is appropriate.
The SQL Scan schedule step takes a required Environment property, and should also be tagged to Panel Service instance(s) that have permissions and connectivity on the target database.