Thanks. 

(you got a good moniker too...) 

All right then, if he's restin', I'll wake him up! (shouting at the cage) 'Ello, Mister Polly Parrot! I've got a lovely fresh cuttle fish for you if you show...

Winslow?!  WINSLOW?! 

Know what I mean? Say no more...

The parrot is dead! It is no more!...

Young punk....   (of course I was just a child..., but I 'may' have been able to pull a trigger...). 

I think they are...

Could test for Existence and then find the next ID.  That would probably make for a procedure hit during the save process, but it could be better than not allowing...

Damned if I know.  This is one of those prove you did not kill Kennedy, (i.e., prove a negative).  As I have stated in the past, our DBA is a...

I started a new thread on this for information on QUERY_GOVERNOR_COST_LIMIT. 

My original thread indicated this is not my data, so I am not familiar with it.  Basically, I was...

Thanks Remi.  We already thought of that option, but it is too restrictive, (not dis-similar to my KILL approach if the SPID runs too long). 

On occassion there are legitimate...

Thanks Noel.  I did not realize you were trying to persuade me not to use this method. 

Unfortunately, that leaves me back at space 1 with no solution to preventing...

Thank you!  That seems to be only one of the two references on MSDN. 

I was hoping to learn more about how to determine a general value for the upper...

<href="Curses'>http://www.sommarskog.se/dynamic_sql.html">Curses & Blessings of Dynamic SQL

man - I can never get this 'simple' html to work.... 

SQL Server will cache the Query Plan, so subsequent runs of the same, (or very similar) queries should return results quicker.  But, it does not cache the results. 

Can you...

Perfect reply!  Thank you.  I assumed it was a total cost on the SPID, not on each query.  That makes total sense.  Thanks. 

Thanks Noel!  Wholeheartedly agree about not setting this server wide.  That is why I want to use a number, but I still can't figure out how to actually use that...

The following returns 999,999 records...  Not sure what setting the value to 20 means, (I got the same results when I set it to 2)... Query Analyzer indicated 0:04:37 seconds. ...