yep - that line updates the view count for the topic your in. It therefore locks the database for a split second.
I think I may have found the root cause of everything though now. Large searches of profiles are taking 15+ seconds now that we have so many members. The main cause of this is the sheer amount of postcodes it's searching through (And comparing against profiles). When someone runs a search, it locks the database for that time period! Hence nobody else can then get in (i.e. to open the forums, etc)
To try and work towards a fix now, i'm going to change the scripts so that you CANT search for any more than 50 miles.
We can all monitor it over the weekend and see if we still get the error.
that updates the last time you were active.
You got in there before i fixed the problems though. :-)
Try from now on.
PS: Does a 50 mile radius limit bother anybody in the searches? Surely 50 miles is a lot? Just until I find a solution
nationwide is easy to do, because it means simply no narrowing down, I can add that tonight.
The problem is when searching, say 200 miles, because that means that 2000+ postcodes have to be filtered through against the profiles. Each postcode takes time to filter.
50 miles searches in about 2 seconds which is ok. Nationwide will be QUICKER because I wont have to filter the profiles at all :-) Leave it with me
Just got this one Matt at 17.38ish!
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 91) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 67
and this one at 17.41!!!!
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 85) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/posts.asp, line 199
offs!!!!!!!!!!!!!!!!!!!!!!! 17.44
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 135) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 187
arrrrrrrrrrrrrrrrggggggggggggghh!!! 17.54
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 135) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 187
Damn I got it now...
Microsoft OLE DB Provider for SQL Server error '80004005' Transaction (Process ID 133) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. /sites/bm/forum/all_topics.asp, line 125 19:20 on 10th August
yea, i think it was being caused by big searches (People searching 100+ mile radius). It locks the site temporarily.
Never used to notice because there werent so many people using the site at once.
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 99) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/chat/Usersdata.asp, line 13
just got this at 21:20
Look wot I just got Matt @ 22.12
Microsoft OLE DB Provider for SQL Server error '80004005'
Transaction (Process ID 148) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.
/sites/bm/forum/all_topics.asp, line 125