Microsoft – SQLServer – Expensive Query – “fetch next from dbmCursor into @database_id”
Reviewing a couple of MS SQL Server Instances and one of the Queries that was cited as expensive is:
fetch next from dbmCursor into @database_id
Was not so sure where it came from.
So Google for it and found it here:
So it looks like it is part of “Database Mirroring Monitor Job”
So if you deem it a bit expensive, review your “SQL Server Agent” jobs and disable “Database Mirroring Monitor Job”.