Piling on at this point, but what the heck...

TSQL is easy. WAY TOO EASY.

Developers look at it, learn the syntax and, as far as they're concerned, they're done. What they...

One guess. When running the query from Management Studio, do you have hard coded parameters like this:

DECLARE @MyParm int

SELECT...

FROM dbo.View

WHERE SomeColumn = @MyParm

Then of course the proc might look...

VARCHAR(MAX) probably needs to be streamed to ODBC, but I would think the max value would be a page worth of data, 8000, not 256 characters. I haven't seen a...

Don't bow. You're right. 100%.

I think most of us have been focused on the indexes. I'm still a bit bothered by the cluster being on such non-selective columns. It's not...

Same here. Don't put this stuff in master. Don't...

Same here. Can you generate execution plans for the two queries? Estimated of course since you don't want to wait for 10+ minutes again.

Generally, don't use them. Ever. Yes, there are exceptions to that rule, but you need to be extremely careful when deciding you have an exception. You may not actually have...

Nope. GO is an external construct for scripting within SSMS, not an actual part of TSQL as such. How about COMMIT TRAN?

Oooh! I may have to try that just to see what happens. I'll bet you looked great on that one. But here's a question, how long did it take you...

OK. Jack's explanation is more clear. Go with that one.

GO acts to close off open transactions.

Thanks! I've been practicing.

Whatever the DTS package is doing, the transaction is so large that it's filling the log file. Break the transaction down into more discrete parts so that you get...

First, you've got one index that's completely a waste (there may be more). Index 11 eliminates the need for index 7 because they both have the same leading edge. So...

Queries submitted to SQL Server go through a process called the optimizer. It makes decisions based on the data in the database as to what order to do certain processing...