I imagine that this is an issue that I need to bring up with the application vendor, but I thought I'd ask here for any ideas.
One of our applications (a windows service which acts as the middleman between SQL Server and other devices) uses cursors to fetch information. Usually, these are open for a moment or two. Lately, it'll occasionally hold open hundreds of sessions and hold these cursors for over an hour.
When I look using Jonathan Kehayias's "whoisactive" procedure to get an overview, I show all of these tasks as SLEEPING, but with very little CPU used, and generally a grossly large number of reads on the database. This is NOT a big database; this information should be available fairly quickly. They all show the same querytext: "FETCH API_CURSOR0000000000000007"
In Activity Monitor, I see the processor at 5% max... almost no...