2 new output tables.
One for tracking the most recent cycle start for each of many SA servers:
CREATE TABLE [isweb].[tableSAMostRecentCycleStart] (
[IDKey] [int] IDENTITY (1, 1) NOT NULL ,
[SAID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[MostRecentCycleStart] [char] (14) COLLATE SQL_Latin1_General_CP1_CI_AS
NULL
) ON [PRIMARY]
One for tracking the time spent in all 7 statuses as well as cycles in that
staus:
CREATE TABLE [isweb].[SARunningTimes] (
[IDKey] [int] IDENTITY (1, 1) NOT NULL ,
[SAID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
[UniqueID] [numeric](18, 0) NOT NULL ,
[HostID] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
[S1Min] [float] NULL ,
[S2Min] [float] NULL ,
[S3Min] [float] NULL ,
[S4Min] [float] NULL ,
[S5Min] [float] NULL ,
[S6Min] [float] NULL ,
[S7Min] [float] NULL ,
[TotalMin] [float] NULL ,
[LastCheckDateTime] [datetime] NULL ,
[PreviousCheckStatus] [int] NULL ,
[CurrentStatusCycles] [float] NULL
) ON [PRIMARY]
This is what I create via triggers in MS SQL Server, and it would be a useful
addition to those users who have larger
implementations.
Michael D. Shook
Technical Analyst
[EMAIL PROTECTED]
863 668 4477 (work)
863 860 4070 (cell)
863 665 1261 (fax)
www.saddlecrk.com
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx
> Sent: Tuesday, December 06, 2005 8:39 AM
> To: [email protected]
> Subject: RE: [SA-list] Feature Request 1 - memory of downtime
>
> The cycle number will indeed start from 1 again.
> The question was about the status change time and the status,
> and that is kept.
>
>
> Dirk.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of per ohlsson
> Sent: Tuesday, December 06, 2005 2:36 PM
> To: [email protected]
> Subject: RE: [SA-list] Feature Request 1 - memory of downtime
>
> Hello Dirk,
> Are there any thing else to do?
> Running build 5.0.1856 and have added the key as below.
>
> Restarted Salive and let it run for 3 rounds. Then I did a
> Save and Exit. Restarted Salive and it started from 1 again.
>
> Anything I missed??
>
> Best regards
> Per
>
>
> >>> [EMAIL PROTECTED] 2005-12-05 17:00 >>>
> That can already be done in the builds AFTER the 5.0.1748
> (http://beta.woodstone.nu/soft/salive51.exe)
> HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers
> Alive\StartUp\LoadStatusfromFile (reg_sz) with a value of 1
>
>
> Dirk.
>
>
>
>
>
> _____
>
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of
> [EMAIL PROTECTED] Sent: Monday, December 05, 2005 2:52 PM
> To: [email protected] Subject: [SA-list] Feature Request 1
> - memory of downtime
>
>
>
> When SA is restarted (usually because the server itself is
> restarted), the "down since" "timer" for how long a check has
> been down is restarted.
> It
> would be tremendously useful if SA could keep this
> information alive between restarts. (I dare say this could be
> done using RRD or syslog or something, but it would save a
> lot of headaches if it were done internally).
>
> Thanks,
>
> Ian _________________________________
> Ian K Gray
> OEL IS - European Infrastructure Support
> Tel: +44 1236 502661
> Mob: +44 7881 518854
> 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
