Not if you only use the uptime logging. The link can be made with the other
logging or with the HTML output.
Dirk Bulinckx.
-Original Message-
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of
[EMAIL PROTECTED]
Sent: Thursday, March 13, 2008 2:25 PM
To: Servers
Is there a way to link the server name / pretty name of the monitored device
with the 'uniqueid' field when logging to an ODBC database for the 'uptime
logging'?
The reason I ask is because I now have the uptime logging working to a SQL
database but when I look at the information that is collected
Yes, totally my misreading of the screens. The logging to database screen
where it says 'create table' I was reading as 'create database' so definatly
my fault!!
Thanks again to everyone for the help.
Pete.
"Dirk Bulinckx" <[EMAIL PROTECTED]> wrote:
> SA uses the db as specified within the ODBC
SA uses the db as specified within the ODBC connection.
By default the ODBC layer will use the default db of that user, you can however
via the ODBC applet of the administrative tools (of the OS) change it towards a
different DB then the default db.
So if SA is using the MASTER db, then this is
Thanks everyone for the help on this. I have found the problem now by tracking
all transactions going through the SQL box. Basically, I was using the SQL sa
user to connect to the DB and through analysing the transactions you could see
that Servers Alive server was writing to SQL but I still coundn
Our Group policy is fairly basic I think. Nothing is logged in the event log
when SA goes CPU crazy.
Not sure if it’s relevant but to fix the problem I cannot just stop and
restart the SA service as windows complains that the service is not responding.
Instead, I have to kill the SA process fi
