LogoLogo
ReleasesHomepageBlogSlack
2.5
2.5
  • Welcome
  • Concept
  • SQLWATCH Database
    • Requirements
      • Permissions
      • Performance Overhead
      • Storage Utilisation
    • Installation
      • Install with dbatools
      • Install with SqlPackage
      • Install with SSMS
      • Deploy from source code
      • Optional Components
      • Upgrade
      • Removal
      • Downgrade
    • Configuration
    • Known Issues
      • Collation conflict
      • Database drift
      • Login failed error when running disk logger
      • Deadlock when creating database
    • Notifications
      • Checks
      • Actions
      • Reports
      • How To
        • Add or modify check
        • Add or modify action
        • Add or modify report
      • Process Flow
    • Large Environments
  • Central Repository
    • Requirements
      • Performance overhead on the remote instance
      • Permissions
    • Installation
      • Removal
      • Upgrade
    • Configuration
    • Known Issues
  • Power BI Dashboard
    • Requirements
      • Permissions
    • Installation
    • Configuration
    • Known Issues
      • Power BI Load Errors
    • Performance
  • Design Decision
    • Relations
    • Trend Tables
    • Data Types
      • Real Type
    • Primary Keys
    • Data Compression
    • Configuration Items
    • Using Apply instead of Join
  • Reference
    • Data-Tier Application Package
  • Integrations
    • Send notifications to Slack and Teams
    • dbachecks
  • FAQ
    • How do I check if SQLWATCH is running OK?
    • I am not seeing any data in Power BI
    • Can I modify default checks?
    • The app_log is growing fast
Powered by GitBook
On this page

Was this helpful?

  1. FAQ

How do I check if SQLWATCH is running OK?

SQLWATCH contains many components that are invoked by the SQL Agent Jobs or Windows Task Scheduler. Any failures should manifest in these tasks failing.

SQLWATCH also contains a number of default self-checks (checks with the negative IDs) that ensure correct the execution. You can list any problematic checks with the below query. Running this on the central repository will also evalaute all remote instances, including any import errors:

select *
from [dbo].[vw_sqlwatch_report_dim_check]
where 
	(
		-- get all critical and warning checks:
		(last_check_status in ('CRITICAL','WARNING') or last_check_status is null)
		-- but exclude performance and backup checks:
		and check_id not in (
			-43,-37,-36,-34,-33,-32,-30,-29,-28,-25,-24,-23,-22,
			-20,-19,-18,-17
		)
	-- and list any checks that are failing or never run:
	or (last_check_status = 'CHECK ERROR' or last_check_status is null)
)

PreviousdbachecksNextI am not seeing any data in Power BI

Last updated 5 years ago

Was this helpful?