I have a VB application that is supposed to run unattended 24/7 collecting live data. Periodically SQLServer just stops accepting new data.
1. The VB application continues running with no error messages
2. There is nothing unusual in the SQLServer logs
3. There is nothing in the Event log
4. The system this application runs on sits in a secure room with nothing else running on it, and nothing else on the network. The environment is totally dedicated to this process. The system is robust enough to handle the load and there's plenty of hard drive space. The input does fluctuate some, but there are no astronomical bursts of data that should overwhelm the server.
At first this happened just once or twice, and seemed to coincide with times that I was working in the database while the application was still running (exporting data, creating trivial tables, querying existing data) but for the past 2 weeks it has happened every day, sometimes more than once per day. It seems to be deteriorating steadily. I am not a SQLServer expert by any means; is there anything I should look for in system tables?
If it's any use, the VB connection string I use is:
Set myRS = MyConnection.OpenResultset(Name:="Select * from [mytable]", _
Type:=rdOpenDynamic, _
LockType:=rdConcurRowVer, _
Options:=rdExecDirect)
Any help would be most appreciated. It's especially maddening as the whole business is located across the country from me, and all my troubleshooting is done over a PCAnywhere link.
Sheila
1. The VB application continues running with no error messages
2. There is nothing unusual in the SQLServer logs
3. There is nothing in the Event log
4. The system this application runs on sits in a secure room with nothing else running on it, and nothing else on the network. The environment is totally dedicated to this process. The system is robust enough to handle the load and there's plenty of hard drive space. The input does fluctuate some, but there are no astronomical bursts of data that should overwhelm the server.
At first this happened just once or twice, and seemed to coincide with times that I was working in the database while the application was still running (exporting data, creating trivial tables, querying existing data) but for the past 2 weeks it has happened every day, sometimes more than once per day. It seems to be deteriorating steadily. I am not a SQLServer expert by any means; is there anything I should look for in system tables?
If it's any use, the VB connection string I use is:
Set myRS = MyConnection.OpenResultset(Name:="Select * from [mytable]", _
Type:=rdOpenDynamic, _
LockType:=rdConcurRowVer, _
Options:=rdExecDirect)
Any help would be most appreciated. It's especially maddening as the whole business is located across the country from me, and all my troubleshooting is done over a PCAnywhere link.
Sheila