Yeah, we’ve ran into issues with the lock table when set nocount on is set. There is a bug for it, but no work-around yet besides making sure set nocount is off when the lock table is accessed.
For reference, you shouldn’t have to deal with the runInTransaction attribute, it is best to have each changeSet run in a transaction rather than autocommit after each statement (for statement types the DB doesn’t already autocommit). There are some databases that have problems with some statements running in a transaction, but sqlserver is just fine.
Nathan