SQL Server 2008 Running trigger after Insert, Update locks original table

Question

I have a serious performance problem.

I have a database with (related to this problem), 2 tables.

1 Table contains strings with some global information. The

Answer 1

I looked around on the internet, and I couldn't find any way of making the trigger happen without claiming a lock. Therefore I choose to do the inserts via a stored procedure, which in turn performs the logic previously found in the trigger. This allowed me to execute the content of the trigger in a transaction AFTER the actual data was inserted and the insertion lock was lifted.

Hope this helps!