Did you guys notice this thread is two years old ?

Four things to watch out for:

The trigger is incorrectly coded for single-row changes. All trigers should handle multi-row changes.

UPDATE(STATUS) does not means that the status column 'changed' it means that...

Can you post some sample code ?

have a look at *sp_executesql* on BOL.

That KB is *VALID* also for 7.

the 'other' conditions are:

What is "login on" are scripts not people.

These scripts are highly synchronized triggered by cron (Unix)

All happens at once withinn a maximum of 3 MILLISECONDS...

That sounds like a CLIENT side issue. If you need to enforce that on the server Use a view to restrict the columns that can be updated and run the...

In my case 300 *AT ONCE* --- was too many

select into LOCKs the access. You should simply select from the view.

Just make sure you use appropriate WHERE clauses and indexes.