When your Database contains a How would you fix the database to come up again. I have seen that -gf is implemented to disable triggers. Is there somthing like -xyz to disable events from the command line ? Think of the posibilities. Implement a bogus DatabaseStart event and when you bring up your server 3 Month later it is blocked. And you did not try to start you backup database ;-) |
Seems like a deadlock situation...Do you know what exactly crashes the server? May it be possible to connect VERY FAST to the database and drop the event connection or use a somewhat blocking query that could block event execution?
Just to add: Breck has requested an option to disallow connections while DatabaseStart is running, c.f. news://forums.sybase.com:119/iapgv2t5e0ti7of4bbdqcpe7bovhugr8cg@4ax.com. Now imagine you had chosen that option, too :(
Excellent question! FWIW Foxhound actually contains a STOP ENGINE statement in the DatabaseStart event that (gosh, I hope!) only gets executed under certain specific circumstances :)
After I read http://sqlanywhere.blogspot.com/2008/02/defragmenting-temporary-file.html I played with my development environment. If I remember correctly I had a
CALL xp_cmdshell( 'NOWHERE_TO_FIND.EXE')
in that event.