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 |
|
shaminda
Starting Member
25 Posts |
 Posted - 2005-07-28 : 09:55:50
|
| I have a job that downloads data from our AS400 to our SQL Server 2000. On and off the SQL Server service stops when it tries to run the job. The job runs 4 times a day. But I cannot tell when the SQL Server service stops, or why it stops. One day last week it stopped twice. So every time this happens we have to start the job manually. And the only thing the event log says is ‘the SQL Server service stopped unexpectedly’ has anybody seen this problem before? Does anybody have a solution to the problem? Any help would be appreciated. |
|
|
Kristen
Test
22859 Posts |
Posted - 2005-07-28 : 10:35:54
|
| Won't solve the problem, but many services can be set to restart automatically if they stop - we also have an hourly scheduled BATch file that does a NET START on all the "critcial" services just in case the Sevice-Stopped-Watchdog is on strike!Kristen |
 |
|
|
shaminda
Starting Member
25 Posts |
Posted - 2005-07-29 : 08:48:58
|
| Thanks for your suggestion Kirsten. Is there a way to check whether MSSQLSERVICE is running say every 15 minutes or half hour and if it is not running then do a NET START using a batch file? |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-07-29 : 11:19:09
|
| No harm doing NET START even if its already running - it will just given a message to that effect.So just make a BATCH file and schedule it for every 15 minutesSomething like:NET START "MSSQLSERVER"NET START "SQLSERVERAGENT"Kristen |
|
|
|
coolerbob
Aged Yak Warrior
841 Posts |
Posted - 2005-07-29 : 11:51:03
|
| I still can't see why the SQL Server should stop out of the blue. That's sounds pretty serious. If that happened here, I'd be out of a job! |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2005-07-29 : 12:05:36
|
| It hasn't happened to us recently, but it used to happen all the time - and the WatchDog service didn't restart it.Clearly if a job is failing that needs fixing, but if that in turn causes SQL Agent to be stopped then no other jobs run - and that's even worse IMHO!Kristen |
|
|
|
|
|
|
SQLSERVER service stopping unexpectedly