detecting that a SQL db is running
Hi I wonder if anyone can help me with a problem that I have with MSDE SQL db. [I am changing to SQL server soon]. I have an app that runs on a server that communicates with remote devices using email, this and other similar servers then sends XML/SOAP messages to a master application. I am in the process of intercepting these XML messages and forwarding them on to a service managment platform for notification alerts etc. This app reads a SQL db to get some additional information which is also included in the XML message. the problem is that the app on the comms server is an aggregate of modules, that has a tendency to lock up, the server still runs, but it causes the SQL server to stop. This is being worked on by the developers, i expect that it will take some time to resolve. using ASR we just reboot the server when this happens. Using simple SQL statements, i am able to detect when SQL is up and running, and to detect when it has stopped. Is there a simple way to detect if the SQL server has actually started? i had a look at investigating the registry, but to be honest, from the various recipes that i have seen, i haven't a clue what I am looking at, any advice? any information shall be gratefully received kind regards Bill -- http://mail.python.org/mailman/listinfo/python-list
Re: detecting that a SQL db is running
Dennis none of this matters, all i am trying to find out is whether or not the local MSDE is actually running. I put all the other bits in there to try and put some background to it. kind regards bill -- http://mail.python.org/mailman/listinfo/python-list
Re: detecting that a SQL db is running
thank you paul, much appreciated -- http://mail.python.org/mailman/listinfo/python-list
Re: detecting that a SQL db is running
On Sat, 02 Dec 2006 07:39:51 GMT, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote: >On Sat, 02 Dec 2006 09:02:43 +1300, bill ramsay <[EMAIL PROTECTED]> >declaimed the following in comp.lang.python: > >> Dennis >> >> none of this matters, all i am trying to find out is whether or not >> the local MSDE is actually running. >> > From my reading of your system, you have multiple "local MSDE" >server processes distributed about, and something on those distributed >systems that causes the initial problem... So I've never been clear of >just where any given application/server process actual resides... > > However, all the tests I've been able to perform on my desktop >indicate that /I/ get time-outs or failure to connect messages within 15 >seconds of a connection request when the server process is running. > > I don't get unending lock-ups... dennis it doesn't matter what is causing the lockups, it's a problem with a supposedly professionally written application package that I have no control over. I am just at this moment trying to deal with the consequences. I think that I haave found a way to deal with the issue that I have. Kind regards Bill -- http://mail.python.org/mailman/listinfo/python-list
