OK, thanks.
I thought I hade been through the list, but to quick.
Took a new round, and this entry from Andy Raybeck was what I missed
before I posted my message.
Sorry. I should have studied the list more carefully before I posted..
You are correct. the design of the SELECT * FROM EVENTS was intended
to present only events for today (just like QUERY EVENTS). However,
I agree that the design ought to be changed to reflect the SQL
standard: that is, SELECT * FROM <anytable> presents *all* records
in that table, not just certain ones. In the case of QUERY EVENTS,
you can query events as far back as you want, but the status may
be "uncertain" if the events go back further than your event record
retention setting. So in my opinion, SELECT * FROM EVENTS should
show you all events that are available within the event record
retention timeframe.
This is a change I am lobbying for with the server developers.
Regards,
Andy
I hope your lobbying will work!
On Fri, 1 Dec 2000, Alex Paschal wrote:
> Hello, Tom. The searchable archive (www.adsm.org) has a few examples of how
> to answer this question. I used "sql select time date event actlog" as my
> search string, and I came up with a bunch of messages. Here are just a few;
> I would recommend going to the archive yourself and searching for something
> that might be more specifically suited to your needs.
>
> http://msgs.adsm.org/cgi-bin/get/adsm9811/988.html
> http://msgs.adsm.org/cgi-bin/get/adsm0010/191.html
> http://msgs.adsm.org/cgi-bin/get/adsm0008/487.html
>
> By the way, has anyone else noticed they have a "spiffy" new interface at
> the web site?
>
> Thanks,
> Alex Paschal
> Storage Administrator
> Freightliner, LLC
> (503) 745-6850 phone/vmail
>
>
> -----Original Message-----
> From: Tom Tann{s [mailto:tom.tannas AT USIT.UIO DOT NO]
> Sent: Friday, December 01, 2000 10:09 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: TSM-SQL-question..
>
>
> Yes, I know. This is similar to my example.
> However, I want to something similar to q event begint=now-24, which is a
> generic thing, rather than using the actual date/time as input.
>
> On Fri, 1 Dec 2000, James Thompson wrote:
>
> > Here is an example that might help.
> >
> >
> > 'select * from EVENTS where scheduled_start>'08/01/2000' and
> > scheduled_start<'08/31/2000'
> >
> > James Thompson
> >
> > >From: Tom Tann{s <tom.tannas AT USIT.UIO DOT NO>
> > >Reply-To: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> > >To: ADSM-L AT VM.MARIST DOT EDU
> > >Subject: TSM-SQL-question..
> > >Date: Fri, 1 Dec 2000 17:59:17 +0100
> > >
> > >Hello!
> > >Any SQL-experts out there?
> > >
> > >I have no experience with sql except from the few things I have learned
> > >from the tsm-implementation.
> > >
> > >I want to query the events-table for avents for, lets say the last 24
> > >hours.
> > >
> > >Just like with the q events, only entries since today 00:00 are displayed
> > >as default.
> > >in the q events you can add begind=today-1, begint=now-24 and similar.
> > >
> > >Is it possible to do the same in a sql-statement?
> > >
> > >I have been playing around a little, but the only way I have come up with
> > >so far is to enter the fromdate explicitely like
> > >
> > >tsm: SUMO>select SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events
> where
> > >SCHED ULED_START \> '2000-11-30 12:13:14'
> > >
> > >works, and I thought also the following wold works, but only returns
> > >entries from after today 00:00:
> > >
> > >tsm: SUMO>select SCHEDULED_START,NODE_NAME,SCHEDULE_NAME from events
> where
> > > cast((current_timestamp-SCHEDULED_START)hours as decimal) < 24
> > >
> > >
> > >What am I missing here?
> > >
> > >Any suggestions/comments on this wold be appreciated..
> > >
> > > Tom
> >
> >
> ____________________________________________________________________________
> _________
> > Get more from the Web. FREE MSN Explorer download :
> http://explorer.msn.com
> >
>
|
