Skip to Content
Former Member
Nov 05, 2011 at 06:47 AM

Workstatus Lock table is huge



The dbo.tblFinanceLock (the workstatus table) contains 7 million records, my guess is that this is too much data, and I think that this causes our system to be very slow (we run regularly full and lite optimizes, so I dont think the slowness comes from fact2 or factwb tables).

My question is: should I leave this table as it is ? can I delete any "old locks" without risk ? How to identify them and is there any query you can suggest that does that ?

Thank you in advance