All over our site, and completely intermittent in different places, we get a lock on the UFRecordDataString table, resulting in the following error:
umbraco.DataLayer.SqlHelper [System.Data.SqlClient.SqlParameter, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] - [Thread 81] Error executing query DELETE FROM UFRecordDataString where [key] = @key;
System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 56) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.
As I understand it, this is because two threads are locking the same table at the same time, but as this is inside the umbraco.DataLayer.SqlHelper assembly, there is not much can do?
I've seen similar threads to this, especially removing the primary key on inserts where there is a very similar error - but I can't see how this would help on deletion locks?
umbraco.DataLayer.SqlHelper - DELETE FROM UFRecordDataString [Lock Issue]
Umbraco 7.2.4 Umbraco.Forms.Core 3.0.21.0 Umbraco.DataLayer 1.0.5557.19141
All over our site, and completely intermittent in different places, we get a lock on the UFRecordDataString table, resulting in the following error:
umbraco.DataLayer.SqlHelper [System.Data.SqlClient.SqlParameter, System.Data, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]] - [Thread 81] Error executing query DELETE FROM UFRecordDataString where [key] = @key; System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 56) was deadlocked on lock | communication buffer resources with another process and has been chosen as the deadlock victim.
As I understand it, this is because two threads are locking the same table at the same time, but as this is inside the umbraco.DataLayer.SqlHelper assembly, there is not much can do?
I've seen similar threads to this, especially removing the primary key on inserts where there is a very similar error - but I can't see how this would help on deletion locks?
Regards James
is working on a reply...