That's the reason the WITH ENCRYPTION is provided, I guess. Tried some queries on google, but couldn't come up with anything useful.

You can't use parameters in a stored procedure that you execute using dynamic SQL. The problem lies in the scope of the variables. Same problem when trying to return values...

Haven't got a clue about performance.

But I suppose that SQL Server cashes the (decrypted) SP in memory.

If performance is an issue for you, remove the WITH ENCRYPTION option. As stated...

Same idea as Jeremy, but without using cursors.

Step 1 : Insert all the data in a (temporary) table that has an identity column. Make sure the data is sorted correctly.

That solution is OK for QA. But remember that if anyone executes the procedure outside of QA, nothing is returned! Not to mention the performance hit due to the use...

Is the effect of maxdop 1 not the same as setting the parallelism to 1 processor?

Or do you suspect that there are problems with other queries that use multiple processors?

This sound logical. Query optimizer 'knows' that you don't need the values.

How about joins themselves? Is there a difference in performance if you put more fields in the SELECT than...

BTW, there should be some scripts or threads around that give an encryption algorithm in T-SQL. Think it was 3DES or MD5.

But I have to agree that the best way...

Like ianscarlett said, that is a CLIENT thing. The results are not returned in a grid, nor in a 'text' mode.

They are returned as a recordset (I presume).

So, suppose someone...

Don't think it is possible to set the format in Query Analyzer to 'Text' from a T-SQL command.

You can set the default for any new connection to display results in...

Are you running your query on a SMP machine? How many processors are you using (without the maxdop 1 hint)?

Can you post the query? Maybe there are some optimisations that...

Tried it, and the inserted table is NOT cleared, as I was expecting. Has to be something else.

Maybe try substituting the join conditions to make sure there is a record...

To test this, just insert the values from the INSERTED table into another table.

Do this before and after the first query. Maybe you will see what is happening than.

You could use CryptoAPI to encrypt the password. Comes with any (recent) version of Windows.

It has a bunch of symmetric and asymmetric algorithms that have been proven to be 'safe'.

You...

Are there any triggers defined on the table for delete? Maybe one of those is blocking the statement.