Idea ID: 2699108

Add the hextoraw functionality to improve the CI history information tab response

Status : Delivered
over 1 year ago

The UCMDB is already using the hextoraw function over the 98+% of the time, The recommendation is to set that function at the 100%  of the sql querys to avoid the impact over the UCMDB performance.

Performance: Modify the queries to set the hextoraw function (as per almost all the queries in UCMDB)

Original Query, access index by start_time

SELECT ID,CMDB_ID,END1_ID,END2_ID,START_TIME,CHANGE_TYPE,CHANGER_INFO,CHANGER_DATASTORE FROM HDM_190710COMPOSITION_1

WHERE 1=1 

AND START_TIME >= :v0   AND START_TIME <= :v1  

AND HDM_190710COMPOSITION_1.END1_ID IN ( :v2 )

AND HDM_190710COMPOSITION_1.CHANGE_TYPE IN ( :v3 ,  :v4 ,  :v5,  :v6 )

 

Tune query , access by end1_id

SELECT ID,CMDB_ID,END1_ID,END2_ID,START_TIME,CHANGE_TYPE,CHANGER_INFO,CHANGER_DATASTORE FROM HDM_190710COMPOSITION_1

WHERE 1=1 

AND START_TIME >= :v0   AND START_TIME <= :v1  

AND HDM_190710COMPOSITION_1.END1_ID IN hextoraw( :v2 )

AND HDM_190710COMPOSITION_1.CHANGE_TYPE IN ( :v3 ,  :v4 ,  :v5,  :v6 )

 

Case: SD02532257 Performance: Modificar el código para agregar la función hextoraw

 

Tags:

Labels:

Optimization
Parents Comment Children
No Data