I am getting Deadlocks on the table TW_PROD_SEARCH.
Has anyone had this problem before? if so what was the cause...how did yo fix it?
it is web api table, only use by web users.
interesting, how can you involve the deadlock?
1, deadlock can happen anytime.
2, you can choose a vitim manually with a right click on a process select "Kill Process"(in 'Activity monitor' under management) or SQL server will choose it for you.
if the TW_PROD_SEARCH is too large. you can delete some old records.
even
truncate table TW_PROD_SEARCH
it will be populated by web api.
or you can manually populate it by copies with different spid
Aaron,
We were receiving deadlock errors too but they disappeared when we installed the 8.0.0.3 patch. I don't know if you are on this version yet but it helped us.
Naomi
here is fixed item from Tessitura_v8003_Fix_List.doc
887
Internet
In some cases TP_PROD_SEARCH, which is used by several API calls as well as for the Product Search window performed very slowly, especially when a constituent had rows in the interests table (TX_CUST_TKW). This has been fixed.
Bug Fix
8.0.0.2
11/10/2008
I think it was fixed by this TP_PROD_SEARCH updating.