Nuts. Sorry Chris. I didn't realize that wasn't the OP reporting a different problem. My apologies.

You need to do what Chris is suggesting, get the execution plan. We can speculate all day why one query runs faster than another (although DISTINCT is an aggregation function...

I'm prejudiced because I work for Redgate, but I think SQL Doc is exactly what you're looking for.

However, Jeff nailed it as usual. To have a...

Deadlocks are best investigated in a 2012 or greater server through the system_health extended event session which is actively running on all your servers by default. Here's an

No, there are no nobs or ways to adjust the behavior of the native intellisense. You can basically turn it on & off and that's about it. However, double check....

If you want to monitor your queries for performance metrics and you really care about individual calls to those queries, not simply an aggregate average of calls, then the best...

If the data is changing though, statistics that are a year old is concerning. I agree with the approach the Chris has to see what has been modified. However, assuming...

In general, I'd say this is a serious problem with the data or the structure, but, you could treat it like versioned data and simply follow one of the approaches...

I could be very wrong, but are you thinking of SQL Prompt from Redgate?

There are several ways to do this. I have an older article on Simple-Talk that explains a bunch of them and shows the performance differences between them. Here...

You're also looking at table scans from this bit of code:

"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"

- Theodore Roosevelt
Author of:

SQL Server Execution Plans

SQL Server Query Performance Tuning