Whoops! 

Thanks for pointing that out

The entire proc is recompiled.  Recompilation occurs for a variety of reasons

a) You make a change

b) SQL Server determines that it is worth recompiling due to changes in databased indices,...

Could you please post your C# code snippet here?  Perhaps you have an error in the SQL string in your C# code that's not immediately apparent.

Or use a full outer join

select 
case when f.dbkey is null then 'In @foo' else 'In @foo2' end as  record_state,
         f.dbkey as...

Whoops - seems you and I are often on here replying to questions at the same time Govinn - seems you corrected your misread while I was typing! 

Govinn, I think you might have misread the question.  The variable stores the table name

Key thing is not to stress about it!

Talk naturally about whatever topics they bring up.  You can do whatever you like - if...

Please don't cross post - continue thread here...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=9&messageid=241460

Cheers.

update vv1 set

For all the times I've done things like this I had never thought of using the table alias in the update statement... Thanks for the syntax

Gee, been a while since I've had a FAT32 system   Good point!

Good to hear. 

Not sure about 1, except maybe recompiling may help?

I can answer #3 easily -

Run dbcc freeproccache

For benchmarking always run

dbcc dropcleanbuffers

dbcc freeproccache

This will ensure that SQL is not caching data...

Thanks for the info - is often hard to explain to customers why such things can go wrong with seemingly no change at all...  At least it wasn't database corruption!...

If you are doing this a lot, you should separate the data into two different columns - one storing dates with time values of 0, and one storing times with...

Part of the beauty of GUIDs is that you can generate the value knowing that it will be unique - so why not generate it in your client code and...