Forum Moderators: open
I am not a database expert so I hope this makes sense.
We run a website with a CMS based on MS-SQL.
Everything generally works like clockwork but there are some cursors our developer has created that our director runs sometimes. They are so intensive it can render the site useless for quite a few seconds.
These reports have soft deadlines i.e. they take 10 seconds but it wouldn't matter it they took 5 minutes. Our general pages have a much harder deadline in that if a page takes to long to load we'll probably lose the customer.
Is it possible to place a delay in a cursor to reduce their detrimental effect on the server?
Thanks - Chris
rule #2: know when to break rule #1
rule #3: engage the services of a DBA with a proven track record
Your problem is totally avoidable. Putting a delay into the cursor processing will actually make it worse.
