DataHub LMS import option (Pre Fu R2 Release)

Owned by Former user (Deleted)
Last updated: Jun 28, 2018 by Conor McCann

New feature added to the DataSetImporter in version iQSonar v4 - Cousteau R3 RC1 DataHub onward.

What has change?

By default the DataSetImporter will not import the Oracle LMS command history and SQL Server command history. This feature will greatly speed up an  import in to DataHub and Customers requiring to do often imports will benefit from it.

How about Oracle and SQL reporting using iQReports?

Unfortunately, not importing the command history into DataHub, iQReports Vendor reports for Oracle and SQL Servers will not display any data, as Reports are carried out using the command history results.

Customers should be aware of this before setting up and executing Import and use the switch to import command history when Oracle and SQL server reports are needed, aka audit purpose etc.

Here is a list of what will be not populated into DataHub EDW DB:

  • All the vendor reports (Oracle LMS & SQL Server) will be empty.
  • 3PTV view won't bring any data.
  • OracleDB_V1 views will produce no data as well.

DataSetImporter switch "-ch" if specified will import all command history for Oracle LMS and SQL Server into DataHub as seen bellow.

NOTE: The switch possition in DataSetImport command is mandatory!! ProjectID set to "0" will import all projects from iQSonar_SE DB.

C:\Program Files (x86)\iQuate\iQDataHub\ETL\Tools>DataSetImporter.exe -projectid 0 -ch
Project ID specified : 0
CommandHistory data included in the dataset
Starting DataSetImporter with default parameter set
Using Microsoft SQL Server: VM-DataHub-V4
Executing project ETL1_iQSonar_Extract package ETL1_iQSonar_Extract.dtsx