July 23, 2004 at 7:03 am
Are there any trouble or negative hints when you use the stored procedure "sp_indexoption" to disallow page locks? I am using them to disallow rowlocks in some tables and no problem had been detected so far, but I found several comments about being carefully when using this option. I experiment many "deadlock" errors. Some SPs uses "insert" in batch, firing triggers that uses "updates" in same inserts, locking the index processes and causing the "deadlocks" when in concurrency with an others "spids". I think that better way is disallow index locks. In my tests this option are full functional. Does any problem may occurs in the future?
July 23, 2004 at 8:35 am
I see some ERP application does that to some of tables. But you really have to resolve the deadloacks from application/database re-design.
July 23, 2004 at 8:57 am
Thanks Allen,
I agree with you but my work is in government organization and there are more than 2000 users and several SPs running with this method. It's amazing since many tables should be change triggers by check constraints. Unhappily I no have a choice in this moment to do this (but I really will do an re-design in future). You see any trouble in apply this solution or I really try to fight to change my mind. SOS. I start in my job less than a month for SQL tuning in an institution where everyone has been done what want. Thanks again and if you have any other suggestion, please help me.
P.S. Sorry for my poor english.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply