• Print
  • Share

SQL Jobs

  • Updated on 01 May 2018
  • 1 minute to read
  • Contributors

BizTalk360 allows the administrators to set the threshold for SQL jobs. They have two threshold options:

  • Expected Job State
  • Expected Last Run State

The best practices for monitoring BizTalk Server jobs is that all jobs should be Enabled and that the last run was Successful, but with a few notable exceptions:

  • MessageBox_Message_Cleanup_BizTalkMsgBoxDb job should be disabled
  • MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb job never ends with success.

BizTalk360 allows you to define the right monitoring conditions for the jobs by assigning an Expected Job State of Enabled for all jobs (except the MessageBox_Message_Cleanup_BizTalkMsgBoxDb) . You should also assign an Expected Last Run State to Successful to all jobs (except the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb).

Setting up monitoring for SQL jobs

  • Log in to the BizTalk360 application
  • Click 'Monitoring' in the navigation panel
  • Click the expand button against 'Manage Mapping' tab and select 'SQL Server Instances' link
  • Select the SQL Server instance for which you want to set up the monitoring on SQL jobs
  • Select the Alarm name (see Creating an alarm) from the drop down for which you would like to associate the alerts
  • Select the check boxes against the SQL Jobs that you wish to monitor
  • Set the value of Expected Job State and Expected Last Run State by selecting the appropriate values from the drop down boxes. For instance, if the current state of the SQL jobs is Enabled and the Expected Job State is Disabled, you need to set the value in the drop down to Disabled. Similarly, if the Last Run State of the SQL Job was Successful, you can set up monitoring over the Expected Last Run State to either Successful or Do Not Monitor state.

BizTalk360-Monitoring-SQL-Servers-Jobs.png

BizTalk360-Monitoring-SQL-Servers-Jobs-Select-Instance.png

BizTalk360-Monitoring-SQL-Servers-Jobs-Monitoring-Enabled.png