We had the same issue. Initially we did not think it was memory bottlenecks since cache hit ratio was around 100. But we increased the server memory and the issues...

I had the same issue. It had to do with a schema changed being applied via linked server. I killed the spid and the blocking was gone..

This could also be due to the fact the log file drive for the SQL Agnet was changed. To fix the issue change the registry to point to the new...