Viewing 7 posts - 1 through 7 (of 7 total)
Gianluca,
I haven't purposely overlooked your example.
The check_db_state output file was getting this message
"HResult 0x2, Level 16, State 1
Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd:...
October 14, 2011 at 9:33 am
Hi I managed to create the procedure in master database
in dbo." " schema
..............................
USE [master]
GO
CREATE PROCEDURE dbo.SQLDBState_Proc AS
BEGIN
...
October 14, 2011 at 6:00 am
Apparently the sql procedure was only complaining because it didn't like
"use master
go"
in the procedure.
I've created the procedure via new query in sql server mgnt studio. So now I have a...
October 14, 2011 at 2:46 am
FYI. As you can see I've shortend the .bat and the sql scripts for ease of use.
October 13, 2011 at 11:41 am
Appologies for the delay in respond. Been on leave...
I can hopefully use both strategies in future.
I'm trying the return by encapsulating the sql in a proc
The proc is meant to...
October 13, 2011 at 11:39 am
Gianluca,
Thanks for your input. I'm sure I would be able to apply your coding somewhere in future.
I also agree with your comment but the monitoring tool we are using requires...
October 12, 2011 at 6:43 am
I have already got a batch script which when an ERRORLEVEL number is returned from a t-sql script (run using sqlcmd from the batch file, would handle the ERRORLEVEL as...
October 11, 2011 at 10:21 am
Viewing 7 posts - 1 through 7 (of 7 total)