At one of customers we see a lot of locking on the "Dimension Set Tree Node" Table.

This is happening because they are creating a lot of (temp) sales lines with multiple price calculations that are based on the Dimensions for their website. (multiple calls a minute)

After investigating the issue we believe a problem is in the GetDimensionSetID procedure in the Dimension Set Entry table.

Here the base app is still using Locktables instead of Tri State locking (I wonder if the Locktable is even needed at this point)

The problem is that the whole table is locked and in my opinion we only need to lock the actual Tree Node Record that is being used. Can this be optimized ?