Re: [ADSM-L] Query performance issue
2011-08-22 12:23:01
Hi Richard,
You're right, and I see a mistake in my statement. I should have written
"date(date_time)=current_date" and not
"date(current_timestamp)=current_date"...
Best regards / Cordialement / مع تحياتي
Erwann SIMON
Le 22/08/2011 13:29, Richard Sims a écrit :
Working with timestamps can be onerous. One sometimes has to be wily to
compensate for processing time. Try:
select msgno, severity, message, originator, nodename, ownername, schedname, \
domainname, servername, sessid, session, process, date_time \
from actlog \
where DATE(DATE_TIME)=CURRENT_DATE and date_time>(current_timestamp - 3
minutes)
Add Order By if you want.
Richard Sims
On Aug 22, 2011, at 3:08 AM, Grigori Solonovitch wrote:
Thank you very much Erwann, but it does not help. There is no visible
improvement.
Grigori G. Solonovitch
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Erwann SIMON
Sent: Sunday, August 21, 2011 4:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Query performance issue
Hi Grigori,
Try to first add a clause that limit the scope of the search to avoid
calculation on the entire actlog table, something like "... where
date(current_timestamp)=current_date and
cast((current_timestamp-date_time)minutes as decimal)<3 ..."
Best regards / Cordialement / مع تحياتي
Erwann SIMON
Le 21/08/2011 12:38, Grigori Solonovitch a écrit :
TSM Client 6.2.3.0& TSM Server 5.5.5.
Is there any way to speed up next request?
select msgno, severity, message, originator, nodename, ownername, schedname,
domainname, servername, sessid, session, process, date_time as
date_time
from actlog
where cast((current_timestamp-date_time)minutes as decimal)<3
ORDER BY date_time DESC
Thank you very much in advance.
Grigori G. Solonovitch
|
|
|