Key questions about this property
The answers below summarize the purpose, scope, default effect, and review scenarios for this property.
| What does it do? |
It defines the record count threshold above which chunking is enforced during deletions and updates, ensuring efficient handling of large datasets. |
| What area does it affect? |
Database performance management |
| What does the default mean? |
No default value is stated in the ServiceNow documentation. |
| When should you review it? |
Review this property when managing large tables or optimizing database operations. |
Property record
Facts stated in the ServiceNow documentation. No out of the box record has been read from an instance yet.
| Property name |
glide.db.forced.chunk.threshold |
| Type |
Not stated |
| Application |
Not stated |
| Default value |
Not stated |
| Description |
Not stated |
Sources
Official references and nearby text excerpts where this property appears.
Context preview
Snippet 1
... with large tables. The setLimit() method does not limit the number of records that are deleted with deleteMultiple(). All records returned by the query are deleted regardless of setLimit(). The glide.db.forced.chunk.threshold system property sets the threshold above which forces chunk record deletions and updates. Chunking helps to prevent non-primary key deletions on huge tables from causing replication problems. For more information, ...
Context preview
Snippet 2
... table. glide.db.audit.ignore.delete Specifies the tables where the sys_audit_delete file is not updated when records are deleted. • Type: string — comma-separated list of tables • Location: System Property [sys_properties] table glide.db.forced.chunk.threshold Sets the threshold above which to forces chunk record deletions and updates. Chunking helps to prevent non-primary key deletions on huge tables from causing replication problems. Use this property to ...
More in glide.db
Other properties in the same namespace.
All 59 properties in glide.db →