User the value here, request_owner_id , to look at sys.dm_exec_requests. From there you can join to sys.dm_exec_sql_text or whatever else you need to understand what's happening with that lock.

Normally, I completely prefer a side-by-side upgrade. Get 2012 on a different server then move things to it. I find it to be a much safer and more consistent operation....

You're experiencing I/O waits during I/O operations... The only way to speed that up is to get faster/more disks.

I've been very happy (mostly) with my Toshiba tablet. But if the Surface comes out at $199, and it's a good form factor, plenty of memory, I think I'll upgrade...

After you run RECOVERY, SQL Server rolls forward or rolls back transactions and puts the database into normal state. You can't then start applying transaction logs again. You need to...

Same answer as Anthony, but since you're on 2008, I'd strongly suggest using extended events instead of trace. They cause much less impact on the server and you can do...

Full backups and transaction log backups are disconnected after the very first time you run a transaction log backup. You can pick any given full backup and use any set...

To get an ERD diagram and do it automatically, I'd take a look at Embarcadero DBArtisan. It has a command line utility, reporting mechanisms, and a scripting language, that will...

Plan on restoring them one at a time. You can open multiple windows and start multiple restores, but you'll see very poor performance. Better to know the order that you...

If the massive slowdown was just for the first few hours, I would assume it had something to do with caching. But since you get slow behavior for up to...

In addition to setting the Max Degree of Parallelism, make sure you change the Threshold for Parallelism setting too. The default value of 5 is way too low. I'm not...

GilaMonster (8/13/2012)

---

Assuming of course that the procedure's plan was ever cached, has not been aged out of cache and the SQL instance hasn't been restarted since

The plan cache will give...

It sounds like a case of bad parameter sniffing. This occurs when a particular parameter value is used and the statistics are different for it than for the hard-coded value....

It's a less than perfect approach, but you could simply query sys.dm_exec_query_stats (or if you really are only interested in procedures, then sys.dm_exec_procedure_stats) and order by the last execution date...

Just curious, but that's a really odd question. Why do you need that in order to...