SELECT Count(isweb_salastcycle.hostid) AS [Count], isweb_salastcycle.description,
isweb_salastcycle.hostid
FROM isweb_servalivestats INNER JOIN isweb_salastcycle ON isweb_servalivestats.hostid
= isweb_salastcycle.hostid
GROUP BY isweb_salastcycle.description, isweb_salastcycle.hostid,
isweb_servalivestats.status, isweb_servalivestats.timing
HAVING (((isweb_servalivestats.status)=1) AND ((isweb_servalivestats.timing)=0))
ORDER BY Count(isweb_salastcycle.hostid);
returns
{see attached}
Mike
>>> [EMAIL PROTECTED] 01/07/04 02:30PM >>>
Is it always the same ping check that gives the non 0 results?
Dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Michael Shook
Sent: Wednesday, January 07, 2004 8:16 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] DB logging error
Minutes. While that does change the datediff calc, the rest should be valid.
Mike
>>> [EMAIL PROTECTED] 01/07/04 01:55PM >>>
And what are you using as unit?
Dirk.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Michael Shook
Sent: Wednesday, January 07, 2004 7:02 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] DB logging error
According to my db,
SELECT COUNT(*) AS Expr1
FROM servalivestats
WHERE (status = 1) AND (timing <> 0)
returns 84
SELECT COUNT(*) AS Expr1
FROM servalivestats
WHERE (status = 1) AND (timing = 0)
returns 408
Looking into the data, there is only one instance where timing wasn't = 0
and the test was a ping test. Where the timing was equal to zero, there was
a mix of tests.
SELECT CONVERT(datetime, previousstatuschange) AS pdate,
CONVERT(datetime, laststatuschange) AS ldate, DATEDIFF(ss, CONVERT(datetime,
laststatuschange), CONVERT(datetime,
previousstatuschange)) AS myDiff, timing
FROM servalivestats
returns a zero value for most myDiff (a dozen or so were actually negative
values, but were -9 or more).
SELECT COUNT(*) AS Expr1, previousstatus
FROM servalivestats
WHERE (status = 1) AND (timing = 0)
GROUP BY previousstatus
returns
4 , 3
74, 4
330, 5
I don't use the timing value since it gets reset if SA gets reset (I run a
calc externally on every check and track those values in a seprerate db), so
I didn't notice this.
Hope this helps
Michael Shook
Technical Support Analyst - Corporate
Saddle Creek Corporation
723 Joe Tamplin Industrial Blvd
Macon GA 31217
478 742 8740 ext. 105 (work)
478 256 9318 (mobile)
478 742 7917 (fax)
[EMAIL PROTECTED]
http://www.saddlecrk.com
>>> [EMAIL PROTECTED] 01/07/04 11:49AM >>>
anybody else having problems with the statistical odbc logging that the
timedifference field is always 0?
Dirk.
_____
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
Of Ahmed Hassan
Sent: Wednesday, January 07, 2004 5:42 PM
To: [EMAIL PROTECTED]
Subject: RE: [SA-list] DB logging error
I didn't try MS Access because I use SQL and will rather like it to work
with SQL as before.
_____
<http://uk.rd.yahoo.com/mail/tagline_messenger/*http://uk.messenger.yahoo.co
m> Yahoo! Messenger - Communicate instantly..."Ping" your friends today!
<http://uk.rd.yahoo.com/mail/tagline_messenger/*http://uk.messenger.yahoo.co
m/download/index.html> Download Messenger Now
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
To unsubscribe from a list, send a mail message to [EMAIL PROTECTED]
With the following in the body of the message:
unsubscribe SAlive
Count description hostid
1 ping 1220
1 ping 200
1 URL : http://10.10.150.33/IISFunctionCheck.htm 20202
1 SQL Server (db PRD1) 20205
1 external COM check (ODBC Query addon) 20350
1 ping 226
1 ping 227
1 ping 228
1 ping 222
1 ping 231
1 ping 232
1 ping 238
1 ping 240
1 ping 244
1 ping 622
1 ping 651
2 ping 650
2 ping 230
2 ping 241
2 ping 242
2 ping 243
2 ping 239
2 ping 235
2 ping 237
2 ping 223
2 SQL Server (db PRD1) 20209
3 ping 221
3 ping 421
3 ping 422
3 ping 423
3 ping 424
4 ping 425
4 ping 426
4 ping 246
4 ping 285
4 ping 229
4 ping 720
5 ping 600
6 ping 400
7 ping 800
8 ping 721
8 ping 234
9 ping 1200
10 ping 30001
15 NT Process : serversalive 30101
16 external COM check (ODBC Query addon) 20352
23 ping 700
226 external check (C:\Program ) 20201
