This wait accumulates while SQL Server is executing the WAITFOR command. As this is an idling wait it is safe to ignore. The WAITFOR command does consume a small number of CPU cycles so it is recommended not to use it excessively

Resolved by


Suggested solutions

  1. If long waits are expected between executions it will be less resource intensive to run as periodically as an Agent job
  2. High values of this wait are safe to ignore

Additional research

Filtering Out Benign Waits

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index