Attix
Attix

Reputation: 115

Rewrite query to use Analytic Functions

I have a Table Events which logs Insert, Update and Delete of Events. See the MWE her: http://sqlfiddle.com/#!4/6c2cb1/1

DDL Statement

CREATE TABLE "EVENTS" 
   (
    "EVENT_ID" VARCHAR2(30 CHAR), --Name of the Event
    "EVENT_LOCATION" VARCHAR2(60 CHAR), --Location on which the event occured
    "EVENT_TRIGGER" VARCHAR2(2 CHAR),  --Trigger which protocolled the event (I,U or D)
    "EVENT_CHANGE_ID" NUMBER,  --Unique Sequence Number
    "EVENT_CHANGE_DATE" DATE DEFAULT SYSTIMESTAMP
   );

INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT1','LOC1','I',1,SYSTIMESTAMP-1);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT1','LOC2','U',11,SYSTIMESTAMP-1);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT1','LOC4','U',117,SYSTIMESTAMP-1);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT1','LOC7','D',1430,SYSTIMESTAMP-1);

INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT2','LOC1','I',2,SYSTIMESTAMP-1/48);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT2','LOC2','U',131,SYSTIMESTAMP-1/48);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT2','LOC5','D',11337,SYSTIMESTAMP-1/48);
INSERT INTO EVENTS (EVENT_ID,EVENT_LOCATION,EVENT_TRIGGER,EVENT_CHANGE_ID,EVENT_CHANGE_DATE) 
VALUES ('EVENT2','LOC7','D',14430,SYSTIMESTAMP-1/48);

I want to determine the amount of events which have been Inserted at LOC1 and Deleted at LOC7 without any Deletions in between.

SELECT COUNT(*) AS QTY, TRUNC(A.EVENT_CHANGE_DATE) AS DAY
FROM (
    SELECT EVENT_ID, EVENT_CHANGE_ID, EVENT_CHANGE_DATE FROM EVENTS WHERE EVENT_TRIGGER = 'I' AND EVENT_LOCATION = 'LOC1'
    ) A,
    (SELECT EVENT_ID, EVENT_CHANGE_ID, EVENT_CHANGE_DATE FROM EVENTS WHERE EVENT_TRIGGER = 'D' AND EVENT_LOCATION = 'LOC7')
    B
WHERE B.EVENT_CHANGE_ID > A.EVENT_CHANGE_ID AND A.EVENT_ID = B.EVENT_ID
    AND not exists (SELECT EVENT_ID, EVENT_CHANGE_ID, EVENT_CHANGE_DATE FROM EVENTS WHERE EVENT_TRIGGER = 'D' AND EVENT_CHANGE_ID > A.EVENT_CHANGE_ID AND EVENT_CHANGE_ID < B.EVENT_CHANGE_ID and EVENT_ID = A.EVENT_ID) 
group by TRUNC(A.EVENT_CHANGE_DATE)
ORDER BY TRUNC(A.EVENT_CHANGE_DATE);

My naive approach works, however I am wondering if this query could be rewritten using analytic functions. The original Tables contains up to 1 Million records an 3x Full Table Scan is a nogo regarding execution time and performance.

Is it even possible to make this query more efficient with analytical functions?

Upvotes: 4

Views: 88

Answers (4)

Popeye
Popeye

Reputation: 35930

You can use the analytical function SUM to add the 1 to result when it is LOC1 and I and add -1 when it is D, then the final result would be the record having sum = 0 and location as LOC7.

See the answer:

SQL> SELECT EVENT_ID FROM
  2      ( SELECT SUM(CASE
  3                  WHEN EVENT_LOCATION = 'LOC1' AND EVENT_TRIGGER = 'I' THEN 1
  4                  WHEN EVENT_TRIGGER = 'D' THEN - 1
  5               END) OVER( PARTITION BY EVENT_ID ORDER BY EVENT_CHANGE_DATE ) AS SM,
  6               T.*
  7          FROM EVENTS T
  8      ) T
  9  WHERE EVENT_LOCATION = 'LOC7' AND SM = 0;

EVENT_ID
------------
EVENT1

SQL>

Upvotes: 1

Marmite Bomber
Marmite Bomber

Reputation: 21135

Using classic analytic function only.

Filter only the relevant events

(EVENT_TRIGGER = 'I' AND EVENT_LOCATION = 'LOC1')  OR  -- only LOC1 inserts
 EVENT_TRIGGER = 'D')                                  -- all deletes

Then LEAD the next Delete and check the location

with evnt as
(
  select EVENT_ID, EVENT_LOCATION, EVENT_TRIGGER, EVENT_CHANGE_DATE,
    lead(EVENT_TRIGGER) over (PARTITION BY EVENT_ID 
                                  order by EVENT_CHANGE_DATE, EVENT_LOCATION)
      as EVENT_TRIGGER_LEAD,
    lead(EVENT_LOCATION) over (PARTITION BY EVENT_ID
                                   order by EVENT_CHANGE_DATE, EVENT_LOCATION)
      as EVENT_LOCATION_LEAD
  from EVENTS
  where (EVENT_TRIGGER = 'I' AND EVENT_LOCATION = 'LOC1') OR EVENT_TRIGGER = 'D'
)
select 
  EVENT_ID, EVENT_LOCATION, EVENT_TRIGGER, EVENT_CHANGE_DATE,
  EVENT_TRIGGER_LEAD, EVENT_LOCATION_LEAD
from evnt
where EVENT_TRIGGER = 'I'
  and EVENT_TRIGGER_LEAD = 'D' 
  and EVENT_LOCATION_LEAD = 'LOC7'
order by EVENT_ID, EVENT_CHANGE_DATE, EVENT_LOCATION;

Upvotes: 2

Chris Saxon
Chris Saxon

Reputation: 9875

This looks like a good fit for SQL pattern matching:

select * from events
match_recognize (
  partition by event_id
  order by event_change_date
  measures 
    count ( ins.* ) ins_count,
    min ( event_change_date ) dt
  pattern ( ins upd* del )
  define 
    ins as event_trigger = 'I' and event_location = 'LOC1',
    upd as event_trigger = 'U',
    del as event_trigger = 'D' and event_location = 'LOC7'
);

INS_COUNT    DT                     
           1 16-MAR-2020 12:33:58 

This searches for an I(nserts) at LOC1 followed by a D(elete) at LOC7, with any number of U(pdates) in-between.

Upvotes: 2

Lalit Kumar B
Lalit Kumar B

Reputation: 49122

Using LEAD analytical function:

SELECT COUNT(*) as qty,
       TRUNC(event_change_date)day  
       FROM(
            SELECT
                event_location,
                event_trigger,
                event_change_date,
                lead(event_trigger) 
                  OVER(PARTITION BY trunc(event_change_date) 
                       ORDER BY to_number(substr(event_location, - 1, 1))) rn 
            FROM events
) WHERE event_trigger <> 'D'
AND rn <> 'D'
AND event_trigger = rn
GROUP BY trunc(event_change_date);

QTY        DAY     
---------- --------
         1 16-03-20

Logic:

  1. Group each day's events and order them based on the location from 1 to 7 using SUBSTR and get the number from reverse of string.
  2. Use LEAD to compare the event_trigger with it's lead.
  3. The event_trigger in the PARTITIONED group of each date should not have DELETE from 1 to 7.

Upvotes: 0

Related Questions