Edit

Share via

@@IO_BUSY (Transact-SQL)

  • Article

Applies to: SQL Server Azure SQL Managed Instance

Returns the time that SQL Server has spent performing input and output operations since SQL Server was last started. The result is in CPU time increments ("ticks"), and is cumulative for all CPUs, so it may exceed the actual elapsed time. Multiply by @@TIMETICKS to convert to microseconds.

Note

If the time returned in @@CPU_BUSY, or @@IO_BUSY exceeds approximately 49 days of cumulative CPU time, you receive an arithmetic overflow warning. In that case, the value of @@CPU_BUSY, @@IO_BUSY and @@IDLE variables are not accurate.

Transact-SQL syntax conventions

Syntax

@@IO_BUSY

Return Types

integer

Remarks

To display a report containing several SQL Server statistics, run sp_monitor.

Examples

The following example shows returning the number of milliseconds SQL Server has spent performing input/output operations between the start time and the current time. To avoid arithmetic overflow when converting the value to microseconds, the example converts one of the values to the float data type.

SELECT @@IO_BUSY*@@TIMETICKS AS 'IO microseconds',   
   GETDATE() AS 'as of';

Here is a typical result set:

  
IO microseconds as of                   
--------------- ----------------------  
4552312500      12/5/2006 10:23:00 AM

See Also

sys.dm_os_sys_info (Transact-SQL)
@@CPU_BUSY (Transact-SQL)
sp_monitor (Transact-SQL)
System Statistical Functions (Transact-SQL)