This wait accumulates while extended stored procedures are executing. These procedures are deprecated and should not be used for further development. These procedures run in unmanaged memory space therefore can cause SQL Server to crash if not written correctly. Some native functions still use these procedures so some values in this wait are expected

Resolved by

DBAs and Developers

Suggested solutions

  1. Ensure extended stored procedures are written using best practices (link below)
  2. Convert custom extended stored procedures to .net (CLR)

Additional research

How to use extended stored procedures
Common Language Runtime from the DBA Point of View

⇐ Back to index