> For the complete documentation index, see [llms.txt](https://docs.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.collibra.com/data-quality-self-hosted/admin-configuration/admin-console/configuration-settings/admin-limits.md).

# Admin Limits

Admin Limits define the maximum values of parameters passed during the execution of a DQ Job.

![](https://4121921244-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FWCrP7Albs8DfJjIQxUxw%2Fuploads%2Fgit-blob-0ea7b3d80b7b2a0f6e27bae3fe7187dc4751a37c%2Fdq-admin-limits-settings.png?alt=media)

{% hint style="info" %}
You should generally modify the following Admin Limits settings to prevent too much data from being stored in the database. For example, if you set the `datashapelimit` to `50` and the `datashapelimitui` to `25`, when you run a check, only 50 shape issues get stored in the database and only the first 25 records display in the UI on the Findings page.
{% endhint %}

The following table shows the available settings on the Admin Limits page.

<table><thead><tr><th width="152">Setting</th><th>Description</th></tr></thead><tbody><tr><td>categoricallimit</td><td>Limit of categorical outlier storage findings that get stored in the database.</td></tr><tr><td>categoricallimitui</td><td>Limit of categorical outlier findings that display in the UI.</td></tr><tr><td>categoricalscore</td><td>Default categorical outlier score, per record.</td></tr><tr><td>datashapelimit</td><td><p>Limit of datashape storage findings that get stored in the database.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>You can only enter -1, 0, or a positive number for this limit. You can't save until you enter an allowed value.</p></div></td></tr><tr><td>datashapelimitui</td><td>Limit of datashape findings that display in the UI.</td></tr><tr><td>datashapescore</td><td>Default datashape score, per record.</td></tr><tr><td>dupelimit</td><td>Limit of dupe storage findings that get stored in the database.</td></tr><tr><td>dupelimitui</td><td>Limit of dupe findings that display in the UI.</td></tr><tr><td>dupescore</td><td>Default dupe score, per record.</td></tr><tr><td>exportlimit</td><td><p>Limit the number of rows that can be exported. A limit of 0 (zero) indicates that no rows can be exported.</p><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>When exporting <a href="/data-quality-self-hosted/core-concepts/dq-rules.md">DQ rules</a>, the limit applies to each rule individually. For example, if there are 5 rules, the limit applies to each rule; not collectively all rules at once.</p></div><div data-gb-custom-block data-tag="hint" data-style="info" class="hint hint-info"><p>This limit does not apply to Archived Break Records, so avoid using them if you need the export limit to apply universally.</p></div></td></tr><tr><td>fpglimit</td><td>Limit of frequent pattern mining storage findings that get stored in the database.</td></tr><tr><td>fpglimitui</td><td>Limit of frequent pattern mining findings that display in the UI.</td></tr><tr><td>fpgscore</td><td>Default frequent pattern mining score, per record.</td></tr><tr><td>histlimit</td><td>Limit of histogram storage findings that get stored in the database.</td></tr><tr><td>histlimitui</td><td>Limit of histogram findings that display in the UI.</td></tr><tr><td>lookbacklimit</td><td>Limit of lookback intervals findings that get stored in the database.</td></tr><tr><td>maxcellcountforparalleljdbc</td><td>Maximum number of cells for a DQ scan before it is recommended to use parallel JDBC, which gets stored in the database.</td></tr><tr><td>maxcolumnlimit</td><td>Limit of maximum columns display findings that get stored in the database.</td></tr><tr><td>maxconcurrentjobs</td><td>Maximum number of Pushdown jobs that can run concurrently.</td></tr><tr><td>maxexecutorcores</td><td>Maximum number of executors cores to be set during estimation on a DQ scan, which gets stored in the database. Set the default value at the agent level.</td></tr><tr><td>maxexecutormemory</td><td>Maximum number of executor memory (GB) to be set during estimation on a DQ scan, which gets stored in the database. Set the default value at the agent level.</td></tr><tr><td>maxfileuploadsize</td><td>Maximum allowed temporary file size in MB. The default is 15 MB.</td></tr><tr><td>maxnumexecutors</td><td>Maximum number of executors to be set during estimation on a DQ scan, which gets stored in the database. Set the default value at the agent level.</td></tr><tr><td>maxpartitions</td><td>Maximum number of partitions to be set during estimation of a DQ scan.</td></tr><tr><td>maxworkermemory</td><td>Agent Worker Maximum Memory (WMM)</td></tr><tr><td>maxworkercores</td><td>Maximum cores per worker.</td></tr><tr><td>minworkermemory</td><td>Agent Worker Minimum Memory (WMI)</td></tr><tr><td>obslimit</td><td>Limit of observation storage findings that get stored in the database.</td></tr><tr><td>obslimitui</td><td>Limit of observation storage findings that display in the UI.</td></tr><tr><td>obsscore</td><td>Default observation score, per record.</td></tr><tr><td>outlierlimit</td><td>Limit of outlier findings that get stored in the database.</td></tr><tr><td>outlierlimitui</td><td>Limit of outlier findings that get stored in the database.</td></tr><tr><td>outlierscore</td><td>Default outlier score, per record.</td></tr><tr><td>partitionautocal</td><td>Calculate the number of Spark partitions automatically for optimal performance.</td></tr><tr><td>passfaillimit</td><td>Limit of passing or failing threshold findings that get stored in the database. This value is used when passFailLimit is not set in the dataset definition.</td></tr><tr><td>pergbpartitions</td><td>Per 1 GB memory partitions</td></tr><tr><td>previewlimit</td><td><p>Set the maximum number of rows you can preview when you run queries in the <a href="/data-quality-self-hosted/core-concepts/navigation/dataset-overview.md">Dataset Overview</a> and <a href="/data-quality-self-hosted/core-concepts/dq-rules/rule-builder/working-with-the-rule-workbench/create-a-data-quality-rule.md">Rule Workbench</a>. The default value is 250.</p><div data-gb-custom-block data-tag="hint" data-style="warning" class="hint hint-warning"><p>Setting a high previewlimit can strain system resources, potentially causing crashes or unresponsiveness, and can also increase query runtimes, delaying job completion and feedback.</p></div></td></tr><tr><td>rulelimit</td><td>Limits the number of rule break records stored in the metastore for Pushdown jobs. This helps prevent out-of-memory issues when a rule returns a large number of break records. The default value is 1000. This option does not affect Pullup or Pushdown jobs with archive break records enabled.</td></tr><tr><td>schemascore</td><td>Default schema score, per record.</td></tr><tr><td>scorecardsize</td><td>Limit of scorecard size display findings that get stored in the database.</td></tr><tr><td>sourcedupelimit</td><td>Source dupe limit for Pushdown jobs (0 = unlimited)</td></tr><tr><td>sourceoutlierlimit</td><td>Source outlier limit for Pushdown jobs (0 = unlimited)</td></tr><tr><td>sourceoutputenabled</td><td>Source output for Pushdown jobs</td></tr><tr><td>sourcerulelimit</td><td>Source rule limit for Pushdown jobs (0 = unlimited).</td></tr><tr><td>sourcesampleenabled</td><td>Source sample for Pushdown jobs.</td></tr><tr><td>sourceshapelimit</td><td>Source shape limit for Pushdown jobs (0 = unlimited).</td></tr><tr><td>totalworkers</td><td>Total number of workers available.</td></tr><tr><td>valsrcdisableaq</td><td>Disable the Assignment actions (Validate, Invalidate, Resolved) on the Validate Source data model on the Findings page.</td></tr><tr><td>valsrclimit</td><td>Limit of validate source storage findings that get stored in the database.</td></tr><tr><td>valsrclimitui</td><td>Limit of validate source findings that display in the UI.</td></tr><tr><td>valsrcscore</td><td>Default validate source score, per record.</td></tr></tbody></table>

{% hint style="info" %}
Settings with "score" in their name represent the default score for that setting's type of findings.
{% endhint %}
