SQLWatch SQL Agent Jobs or Service Broker Message Queue(s)?

[L0zz]

Hi All,

We've deployed SQLWatch for monitoring all our SQL Servers in our organisation, and I've recently discovered an issue where the SQLWatch_EXEC message queue had messages being processed on it by the [usp_sqlwatch_internal_exec_activated] stored procedure, why I don't know as we normally use SQL Agent Jobs to do all SQLWatch management.

Isn't the default deployment supposed to use SQLAgent Jobs instead of SQL Server Broker Message Queue, why is the SQLWATCH_EXEC queue enabled then?

I can see there are stored procedures for resetting the message queue and switching over to SQL Server message queue based processing:-

[dbo].[usp_sqlwatch_internal_restart_queues]
[dbo].[usp_sqlwatch_internal_migrate_jobs_to_queues]

Do you recommend switching over to using message queue (what are the pros/cons of this?)

Thanks In Advance,

Lozz

[marcingminski]

Hi,

Data collection via broker was meant to replace agent jobs. The idea was so SQLWATCH could work on Azure SQLDB, managed instance (back in the day, it didn't have an agent). You should not be running collection via broker and agent. Pick one.

This [dbo].[usp_sqlwatch_internal_migrate_jobs_to_queues] would have migrated from jobs to queues and enabled queues. If you want to stick with the agent, then feel free to disable queues.