Hi folks, Well, i took the suggestion to install the native drivers and use DatabaseConnectEx (actually used DatabaseConnect() as it allows me to use the profile). When the statement is called (and the SQL Server is not running, the issue we wish to test for) 24x7 seems to hang for almost 2 minutes, then it comes alive and issues a dialog box: "An Error Occurred while executing 24x7 script. Line 2: Unable to connect: SQL Server is unavailable or does not exist. Specified SQL Server not found. Continue testing this job?" When i press [YES] or [NO] i do not receive an e-mail (send e-mail on failed job enabled). Since i am not testing the job, i don't understand the "Continue testing this job?" message. Anyhow, this is not the intended behaviour. Can anyone help? Regards, Mark Richards : This message comes from the ODBC Manager. So don't use it. Instead you can : use the MS SQL Server native driver provided the Scheduler. Make a script : job that : calls : DatabaseConnectEx ... : DatabaseDisconnect : Add notification action that 24x7 Scheduler will execute in case if : DatabaseConnectEx fails. : A better approach is to place 24x7 on the server and have it check for SQL : Server executable files loaded into the memory. You can use "program : is not running" schedule type for such job. : Another solution is to have a JAL script job on the server that will keep : checking the status of SQL Server services. : You can also consider a job using the PING statement.
|