Monitor BizTalk Server Job

The Monitor BizTalk Server job scans for issues, but does not fix them for you! It consist of two steps. First step is the execution of the [btsmon_Inconsistancies] stored-procedure. This procedure will on its turn call other procedures in the MessageBox,
Management and Tracking database to collect error data (like messages without references). The second step is calling the procedure [btsmon_GenerateErrorString] in Management database, which involves a query of two tables [btsmon_Inconsistancies]
and [btsmon_Issues].

Figure 2. Job Properties of Monitor BizTalk Server Job - Steps.

When you query the table [btsmon_Issues] of BizTalk Management Database (BizTalkMgmtDb) you will see the description of the issues that can be detected:

Figure 3. Job Properties of Monitor BizTalk Server Job - Steps.

If job encounters any issues if will fail and return a string containing number of issues found (i.e. result of second step). This string will by default be logged to the event viewer and is also visible in the
Job History.

Figure 4. Monitor BizTalk Server Job History (click to enlarge).

Custom View

Although this job does not fix any issues you can leverage this job by creating a monitoring solution or altering mechanism for administrators so they can act on any issues at hand. This does mean customizations on your part. Either by leveraging the alert
or notification capabilities of SQL Server Jobs or by for instance creating a view that shows any issues. You can create a custom view using the following TSQL code: