One deadlock found so far today - someone tried to run a search on the profiles whilst another person's account was being updated with their "last visited" date and time.
Really don't how how I can avoid these errors - seems impossible
There were a load last night about 11pm UK time.
37 deadlocks yesterday in total, all caused when the database was being updated with the lasted date/time that someone accessed the site (Whilst others were trying to search for profiles, etc).
The 2 jobs conflict and the search gets rejected.
I'm working on a solution
ok I think i've fixed most of it now. I've corrected the searches so that they don't lock the database tables.
Few more changes to make (like to chatroom) before it's all fixed.
Performance will be dramatically improved also after this.
I will be SO happy if I've FINALLY fixed this problem that we've had since day one.
It's been reduced as much as possible by being all on one server (faster), but never totally stopped.
I think now I may have solved it, but I'm not crossing my fingers just yet.
So far I've applied my "fix" to the profile searching and forums (2 biggest used sections). So far no deadlocks today, but yesterday all the deadlocks were at night.
LOADS of changes made! In fact nearly every database command in every page of code has been updated.
And so far... not a single deadlock all day! Brilliant!!!
I know, i know, I'm a genius. lol
Cant upload any pic did have one on but when trying to change it keep getting following error message
Uploaded Photos
Microsoft OLE DB Provider for SQL Server error '80004005'
Cursor updates are not allowed on tables opened with the NOLOCK option.
/sites/bm/myaccount/showphotos.asp, line 156
had this a couple of times lately
Active Server Pages error 'ASP 0113'
Script timed out
/sites/bm/forum/posts.asp
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
had this a couple of times lately
Active Server Pages error 'ASP 0113'
Script timed out
/sites/bm/forum/posts.asp
The maximum amount of time for a script to execute was exceeded. You can change this limit by specifying a new value for the property Server.ScriptTimeout or by changing the value in the IIS administration tools.
![SQL Errors - Need your input (6) - Forums [Biker Match]](/images/backgrounds/strips/8mobileLQ.jpg)
![SQL Errors - Need your input (6) - Forums [Biker Match]](/images/backgrounds/strips/8desktopLQ.jpg)
