Why does GlideAggregate create a limited number of rows?

zsquared
Tera Contributor

Hello,

I was wondering if someone can provide insight on this issue...   I created a GlideAggregate script to count the number of rows of data grouped by a certain column.   I am expecting to see about 150K in new rows to show the aggregate data but the script keeps maxing out at 100,001 rows.   Does anyone know why this could be the case?

10 REPLIES 10

Hi Amlan & Zhen,


This sounds like what I was looking for.   Our instances does not have this property and based on your link of "Available System Properties", the explanation is at the top: "This page describes properties available to an instance. Some properties are available on a system properties form, but some lesser-used properties are only available from the System Property [sys_properties] table. In some cases, the property does not exist in a base instance, but can be added if you need to change the value."   If the property doesn't exist in your instance, I would try and add it and put the value greater than you need it to be.



Thanks,


Trena


Hi zhen.zhu ,



Were you able to have a look at my response?


If I have answered your question, please mark my response as correct so that others with the same question in the future can find it quickly and that it gets removed from the Unanswered list.


If you are viewing this from the community inbox you will not see the correct answer button.   If so, please review How to Mark Answers Correct From Inbox View


Hi everyone,



I updated the sys properties for glide.db.max.aggregate.size but this did


not resolve the issue. Everytime I aggregate a large table, the max results


I get at a time are 100,001.





On Thu, Jun 29, 2017 at 10:48 PM, amlanpal <


mauricio_paloma
Tera Expert

glide.db.max.aggregates is the system property to change. See other community post here:

https://community.servicenow.com/community?id=community_question&sys_id=22dfcf4adb99ab405d782183ca96...

garyopela
ServiceNow Employee
ServiceNow Employee

Hey, I know this is really late, but I was looking through the source code and did find where there is a default maximum level of aggregate rows to return. It is set to 100,000, and can be overridden by the property 'glide.db.max.aggregates.' It returns 100,001 (instead of 100,000) because if checks sets the max row = first row + limit. First row is 1, limit is 100,000, so that's 100,001. Hope that helps.