I agree without there being a "retry logic" in the Web Application its going to sit there and say "Wheres the SQL Server" (AKA Spoof of Wheres the Beef ad from the early 90's".
You could have the service restart, if it runs a script to check and see if the SQL server is up and running ( like SQL ping commandline or a isql/osql script to just check the version number on the server and return an error code ( 0-good, 1=bad, 2=debug) A lot of web applications are like this, Z Edward Ziots CISSP,MCSA,MCP+I,Security +,Network +,CCA Network Engineer Lifespan Organization 401-639-3505 [email protected] -----Original Message----- From: Bonner, John [mailto:[email protected]] Sent: Wednesday, April 14, 2010 9:07 AM To: NT System Admin Issues Subject: RE: Web Service Waiting for SQL Server No compiled 3rd party object. I could write a wrapper but was hoping....quite honestly expecting Msoft to have a solution for what I thought a common problem. -----Original Message----- From: Tigran K [mailto:[email protected]] Sent: Tuesday, April 13, 2010 11:04 PM To: NT System Admin Issues Subject: Re: Web Service Waiting for SQL Server Are you the developer of the service? Why not add the wait or retry in the service code? --Tigran On Tue, Apr 13, 2010 at 1:14 PM, Bonner, John <[email protected]> wrote: > Hello Admins, > > I know this may be a simple questions for you guys but I'm a developer so my > knowledge is not as robust. > > Our web server has a service that relies on communication with SQL server. If > it doesn't see the SQL box Sitescope alarms as the service is not started. > Now this is fine and dandy except during maintenance windows when the servers > get rebooted and the web server comes up before the SQL box does. I know I > could have Sitescope attempt to start the service but I was wanting to be > more proactive and have Sitescope be the backup. So I was hoping there might > be a configuration / dependancy I could specify on that service to not > ATTEMPT it's first start until a check verifies SQL is up. Since I know this > is not a new problem I figured there must be a tried and true method for > handling this scenario? > > Thank You Very Much > JB > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ------------------------------------------------------------ The information in this email may be confidential and is the property of 5280 Solutions LLC. Access to this email by anyone other than the intended recipient(s) is unauthorized. Forwarding, copying or reproduction of confidential information without the express permission of 5280 Solutions LLC is strictly prohibited. If you have received this communication in error, please contact the sender immediately (by reply email) and delete the confidential information from any computer immediately. ------------------------------------------------------------ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
