General ETL Status
See the BigDataInsight Overview Display
Alternatively, a DBA can have a look at the ETLStatus table in the Datamart database.,
Alternatively, a DBA can have a look at the ErrorLog table in the Datamart database.
Other Locations for ETL History
For errors where the ETL is unable to start e.g. due to credential issues, the following methods can be used to see the cause of the issue.
SQL Reporting Scheduled ETL
In a Reporting deployment where SQL Reporting is scheduling the ETL process, the ETL history and results can be viewed in the Autosumm overview display.
Open the Windows Client and connect to the Reporting Server.
In the Navigation pane, find and open the 'Welcome to PROGNOSIS Cross Platform Systems Management' display.
Drilldown on the name of the Reporting Sserver.
From the left-hand Server Navigation, select 'Prognosis Status'.
From the top Navigation bar, select 'Autosumm'.
Find the job with a Source DB of 'BDI<product>DB', where <product> is the name of the deployment, and click on the details link.
This page contains the ETL result history in the Associated Logs window.
SQL Server Agent Scheduled ETL
In a Reporting deployment where the SQL Server Agent is scheduling the ETL process, it is also possible to view ETL history and logs by directly accessing the SQL Agent logs.
Connect to the SSIS Server with SQL Server Management Studio.
In the Object Explorer pane, expand the 'SQL Server Agent' node.
Expand the 'Jobs' node.
Find the SQL Agent job named 'PrognosisBDI_<product>_Start_ETL', where <name> is the name of the deployment.
Right click the job and select 'View History'.
The job's history should be visible, including the results of previous ETL runs, and the log output for each run.