Scheduling the ETL Job via the SQL Server

In a multi-server deployment, it is possible to setup the ETL job using the SQL Server Agent.

The default schedule interval is 15 minutes so that a new ETL job instance is started within 15 minutes of the previous ETL completing. A new ETL instance is started only if the previous ETL instance has completed running. Note that ETL typically takes several minutes or several hours to complete depending on hardware, data volumes, and custom solution in place.

To remove the schedule from the Reporting Server:

Using a text editor, open the <Prognosis_Home>\Server\Configuration\rollupscheduletable.txt file.

Scroll down the file and locate a line similar to the following:

< EVERY 15 MINUTES | W:1-7 | #CurrentNode | <product> | #CurrentNode | cmd:BigDataInsight\UC\SSIS\cmdgwy.bat |||||||| 2017-11-29 14:15:00 ||||| 2017-11-29 14:15:00 || 2 >
Look for the solution name matching the <product> name used in the setup.bat script.

Either delete the line or comment it out by placing an exclamation mark (!) at the start of the line.

To add the schedule to the SQL Agent:

Using SQL Server Management Studio, connect to the SSIS Server.

Using the Object Explorer, expand the SQL Server Agent, and then expand Jobs.

Find the job named 'PrognosisBDI_<product>_Start_ETL', where <name> is the name of the deployment (e.g. UC).

Right click on the job and select Properties.

Select the Schedules page.

Click the 'New...' button.

Follow the wizard to create a new schedule. It is recommended that the schedule be created to run the ETL every hour, or at an interval that is appropriate for the SQL environment.

Exit the properties page.

Right click on the 'PrognosisBDI_<product>_Start_ETL' job, and click Enable.

Provide feedback on this article