If I understand the question... No. You can't pass parameters to a view.

Thanks for the correction. 100% accurate. Apologies for the bit of bad info.

Download the AdventureWorks database from Microsoft. It's a pretty good place for running tests & learning.

http://www.microsoft.com/downloads/info.aspx?na=22&p=1&SrcDisplayLang=en&SrcCategoryId=&SrcFamilyId=&u=%2fdownloads%2fdetails.aspx%3fFamilyID%3de719ecf7-9f46-4312-af89-6ad8702e4e6e%26DisplayLang%3den

There is a lot of time in Itzik's book on graphing & trees & pivots that, in my opinion, won't be used by most people (myself included). However the APPLY &...

I want to jump on the band wagon and recommend Itzik Ben-Gan's "Inside TSQL Querying". Add to it his "Inside TSQL Programming". The first book is all about TSQL queries. The...

Generally, it's probably safer to create the index & temp table together and then add data to it. Clearly it's affecting the locking, but it will also cause recompiles.

SQL Server takes exclusive locks on a row, page or data when it wants to perform a write operation. You've got a process within your stored procedure that is escalating...

It looks like you may be hitting a bug. I found this kb article that seems to describe your situation:

http://support.microsoft.com/kb/935356

"In SQL Server 2005, assertion error 3624 may occur. The...

Good catch. Once I spotted that USING word I couldn't see much else.

Forgive us our typos as we forgive those who typo against us... unless you just ran a restore on the production server...

Cool. What would you use in 2005?

Are you running this against a 2000 server or against a 2005 server in 8.0 compatibility mode? Either of those will be the problem.

One likely issue is the USING word you've got in the very first join. Also, you can't use variables $x. Instead you should use @x. What are those other two...

No, you and the article are correct. Seeks are better than scans. Eliminating, as much as you can, bookmark lookups is the way to go. The issue isn't whether or not...

The differences in the data are most likely going to cause different query plans. I suspect that's the most likely issue.

One thing you said that concerns me a bit. You've created...