August 14, 2006 at 12:25 am
Hi,
In our large organisation we have SQL Server 2000 running on a 2 node cluster using Windows 2000 Advanced Server Clustering. Each node has 2GB RAM. The server has about 10 databases only one of which is significant size at about 1GB. Our website accesses this database via ASP. The website receives between 10000-40000 hits per hour.
The problem is that periodically (not necessarily during high load periods at all) this single database 'freezes' (not the whole server - the other databases seem fine) and refuses all login attempts from the website. This happened again on the weekend when the database was down for about 6 hours. When we go into Enterprise Manager and click on the instance, there is initially no activity for an unusual amount of time but eventually the instance is selected and the tree expands. When this happens everything is ok again and the website can access the database again.
We have only just enabled failure auditing today, so we don't have any info from there and are at a loss as to whats going on. Has anyone out there had similar experiences or have any ideas?
(We will look at upgrading to 2005 and upgrading the machines too but being a big company that will take a lot of time with red tape etc.)
Many thanks.
August 15, 2006 at 10:11 am
Have you tried executing sp_who/sp_who2 in QA when the one database on the server 'freezes' ? You may have blocking issues. Also have you tried executing sp_lock as well ?
RegardsRudy KomacsarSenior Database Administrator"Ave Caesar! - Morituri te salutamus."
August 16, 2006 at 6:32 pm
Hi Rudy,
Thanks for the reply and suggestions,
We haven't tried sp_who2 yet but it is on our list of actions for next time it happens.
Will try sp_lock too.
Cheers, Nathan
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply