tag:blogger.com,1999:blog-497787815177352569.post9206517688744514044..comments2024-01-03T08:55:04.827-05:00Comments on SQL Anywhere: Automatic RestartBreck Carterhttp://www.blogger.com/profile/15975598564711761434noreply@blogger.comBlogger1125tag:blogger.com,1999:blog-497787815177352569.post-20431546473745288902011-02-23T11:50:28.561-05:002011-02-23T11:50:28.561-05:00If memory serves correctly, the UNIX versions of t...If memory serves correctly, the UNIX versions of the server terminate after an assertion failure is reported. Again, if memory serves correctly, I think the motivation for keeping the Windows server up after an assertion failure was to make sure someone using the system was aware that there was a problem rather than hiding just hiding it. That doesn't mean there couldn't be options to control the behaviour.<br /><br />I have a vague recollection that a client app is allowed to shutdown a server that has encountered a fatal error or assertion failure. If so, stopping the server in that state is implementable in client code with the existing software.<br /><br />-john.John Smirnioshttps://www.blogger.com/profile/17831427682756190054noreply@blogger.com