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 |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-08-22 : 07:40:21
|
| Paul Leinweber writes "Info:Our development and Production environments have less than 30 people hitting our SQL Server "box". All our existing applications simply Connect - Do Work - Disconnect - and then clean up our connection in VB (Set it to Nothing).PROBLEM: Whithin days our resources are 50-60% exuasted. For some unknown reason we seam to get connection errors returned while running our code. The errors codes are not consitant or ide provide them. However our error logs in SQL Server never log these connection failures. Logically - I would think that this means that SQL Servers is never even seeing the connection attempts. Our Systems Admin believes that we are doing something wrong and the code is sucking reasources from the machine. However even with 50-60% of the resources being exhuasted I cannot believe SQL Server could not log the connection attempt - regardless of resources used.Questions: 1. Is 50-60% resource utilization unusual? 2. Would resource issues ever keep SQL Server from being able to log a connection attempt and failure? 3. Does that fact that SQL Server cannot log the connection failure imply that something could be wrong with the Client, Wiring, or the Network Hardware in general. 4. The Admin is backing up SQL Server and logs every hour - can this be the source of the problem?Sorry if this is not detailed enough - I am not an admin just a "lowley" software developer :) " |
|
|
jesus4u
Posting Yak Master
204 Posts |
Posted - 2003-08-22 : 07:54:32
|
| Just a thought: Maybe your computers have the lastest WORMS?! Ask your Network Admin to check out that possibility.Alex Polajenko |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-08-22 : 12:46:25
|
| You could run SQL Profiler to prove if the connection is getting to the SQL Server or not. 50-60% utilization is not normal, but you need to figure out why the increase. It could be a worm as Alex mentioned or maybe people are using the application more now. I would suggest running the worm scanner on your network to see if you have any vulnerabilities.SQL Server will not log the connection failure unless you are auditing it. Backing up SQL Server every hour is most likely not causing your problem. We back up our transaction logs every 15 minutes and have no problems what so ever with it.Tara |
|
|
|
|
|
|
Resource / Connection Issues