The lock escalation algorithm seems to have changed in SQL Server 2008, and it no longer kicks in for INSERTs. This means that when inserting large sets of rows without explicitly using a locking hint, we can end up with an equally-large number of locks. This is not good behavior. It wastes a lot of RAM and can cause monitoring software to fail if the software depends on sys.dm_tran_locks to get information. I hope that we can get a fix and return the escalation algorithms to the behavior they had in SQL Server 2005.