So, whom did you help?

He does not need your help on it.

Such a "brilliant" SQL developer will kill all projects without anyone's help.

I can.

And have solved this kind of tasks many times.

Is it your homework?

So, you have to do it.

Table function is probably another solution for you.

I don't think lock is an option at all.

You cannot lock the code, you lock resources used in the code.

If nature of queries in SP will force to apply row...

CREATE PROC MyProcedure

AS

IF Object_ID('tempdb..##MyProcedureTable') IS NULL

CREATE TABLE ##MyProcedureTable (

...

)

ELSE

RETURN

{SP body}

DROP TABLE ##MyProcedureTable

GO

As soon as last connection using ##MyProcedureTable will be closed this table will be dropped automatically.

I don't think mixing syntax is a good idea.

Try to make it consistent:

select count(*)

from nameaddr_ac addr

INNER JOIN recipients rec ON rec.idaccount = addr.id_account and rec.cdeRecipientType = 'Market'

left outer join...

Sorry, being brain dead.

Yvan, who told you that this character does exist?

Yes, it exists somewhere, but why you so sure it does exist for chosen collation?

"CP1" in the name of that collation means...

OBJECT_NAME(@@SPID)

Scope of system functions is limited to the local server.

Since no rows have been inserted or selected locally @@ROWCOUNT returns 0.

Transaction is completed, so nothing to roll back.

It's hard to say if you can restore the data because it depends on many factors you did not show here.

Open BOL...

To make the test right open 10 windows on QA and run the same script from all of them simultaneously.

There are possibly more than one users in the system,...

To avoid false alarms add another check to Peter's solution:

SELECT t.*

FROM Table1 AS t

WHERE t.dteprocesstime = (SELECT MAX(y.dteprocesstime) FROM Table1 AS y)

AND EXIST(select 1 from Table1 AS n where n.dteprocesstime...

Actually using Latin1_General_BIN or any other "binary" collation brings you right result.