Can you expand on that theory??

Yup, is it for reporting or for a permanent table. If it's for a table then I strongly suggest against that design as it is denormalized. A simple...

Where are you creating the #temp table?

if it's inside sp_a, you can't go around a recompile.

Check out this article :

Optimizing Stored Procedures To Avoid Recompiles

You can't do that. You need to use sp_executesql to fetch output values from dynamic sql, and you need to use a stored proc to do that. Sorry...

Are they the same type??

Update table set colb = cola

Still, why would you want to risk that, even in testing you can seriously screw up the server with this?

Why do you need to change the dates?

first turn off allow updates then alt-f4.

Seriouly why would take that chance????

Why do you need to change this setting?

Dito here... I had a single report using 24 objects!!!!!!!!. now it uses only 4 (4 different reports that make a big one).

I'd like to see an exemple of such a proc with 20+ parameters if it's possible.

You're ok. The goal is to forbid direct user access to the table. Sps are a great way to do that.

you can set a default value to the parameter. Then check to see if the value is different so that you know you need to use it. But...

If the missing ids are causing problems with your compagny, then by al means try to correct hit. Like in my case if we have a missing WorkOrder then...

Does it have to be every 6500th row or can it be any rows?

Select top 6500 * from table order by newid().

I'll post other solutions tomorrow.

Insert into dbo.Num (Col order here), values ...

Can you post the code you are using?