Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
tripodal
Constraint Violating Yak Guru
259 Posts |
 Posted - 2008-02-08 : 14:58:59
|
| Good afternoon all. I just barely resolved a connectivity issue with one database. It is the backend for a website which is being hammered.Today we were unable to update the database using code that has worked for the past year.Opening to edit it maxxed 4 cpu's on the SQL 2000 8.00.2039 (sp4) machine. Everything we tried did this, except as reading only.It needed to be updated.The resolution was to detach and reattach said database. (Bad I am sure) my only hunch now is the 27 connections we "cleared" during this process allowed our update to finally work.The question is, how do I find these guys and... close them, debug them? Where would you suggest I start? |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2008-02-08 : 22:30:40
|
| You can get info from master..sysprocesses, it has source machines' mac address and other info. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-02-09 : 14:29:31
|
| You should not have detached/attached the database to resolve the issue. That was unnecessary. You can no longer see what those 27 connections were doing. Next time it happens, check out sp_who/sp_who2 to check for blocking, run SQL Profiler to capture the T-SQL statements, and run Performance Monitor to gather hardware and process information. If you are desperate next time to get rid of the problem, just restart the SQL Server service. Detach/attach should not be used as what happens if the file gets corrupted and you can no longer attach it?Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
tripodal
Constraint Violating Yak Guru
259 Posts |
Posted - 2008-02-11 : 10:46:27
|
| Thank you very much Tkizer and Rmaio, thats exactly the type of information I was looing for. Im sure this will happen again as I didnt "fix" anything. |
|
|
|
|
|
|
27 unknown connections