Hello Balram,
as I understood your situation, query that produces lack returns more that 100 000 rows of data.
OOTB Service Desk interface have limitiation to display only first 5000 rows of data,
so is there real need to make so heavy query and display it on scoreboard?
I don't know your sphere of activity but I also think that having more than 100 000 active requestion makes appreciable system load,
is autoclose configured in your environment?
I can't take my proposals as best practice, but I always recommend to my customers to build stored queries that didn't return more that 3000 rows of data.
You can add timespan option to your query, for example:
from: active = 1 AND (type = \'R\' OR type= \'I\' OR type is NULL)
to:
active = 1 AND (type = \'R\' OR type= \'I\' OR type is NULL) AND open_date > StartAtTime('PAST_YEAR')
This query will show only tickets that were created within past 365 days.
Regards,
Timur