Thanks for your reply.

1. Locking tempdb (is whole db locked) meaning no one can access table indexes.

NO.Locking mechanism work on row level --> page level ---> then table level.no on database level

Not sure i understand that but do you mean the lock is only on affected table?

Also i tried doing the following run an insert statement and put wait for delay '00:01' in it when temporary table is still in scope, then from management studio just select properties of tempdb, i got error time out, once the insert statement finished , i could access tempdb again.

2. My question is more about temporary table created inside trigger, how will that affect in mutli user environment.

4.I am asking should i drop the temporary table in the stored procedure after it finishes using it or just leave SQL handle that?.

Thanks again waiting for you feedback.

Nader