Introduction to the Max Partition Size Check
The Max Partition Size check puts a ceiling on how many records a Scan may load from a single partition. It watches the shape of the load itself rather than the values inside it, which makes it the rule that catches a partition that suddenly ballooned.
This section is the complete guide to the check. The Deep Dive covers the definition, properties, and full evaluation semantics, explains how anomalies are reported, walks through production examples, and collects best practices; the How-tos are step-by-step tutorials for creating, editing, and deleting a check; the API page documents the payload for programmatic use; and the FAQ answers the most frequent questions.
Next Steps
-
How It Works
The complete reference: definition, what a partition is, the maximum partition size property, and why the rule takes no field, filter, or coverage.
-
Anomaly Reporting
The Shape Anomaly the check produces, what the numbers mean, and how partition-level anomalies differ from row-level ones.
-
Examples
Three production scenarios with the resulting anomaly message and the SQL equivalent of what the check evaluates.
-
Best Practices
Guidelines for choosing a threshold, sizing it against real loads, and pairing the rule with its counterpart.
-
Permissions
The team permission each action needs: view, create, edit, archive, restore, and delete.
-
Create a Check
Step-by-step tutorial for creating a Max Partition Size check on a container.
-
Edit a Check
Step-by-step tutorial for changing the threshold on an existing check.
-
Delete a Check
Step-by-step tutorial for archiving a check and deleting it permanently.
-
Troubleshooting
Common problems with thresholds, partition counts, and partition-level anomaly reporting.
-
API
Payload shape and field notes for creating a Max Partition Size check programmatically.
-
FAQ
Short answers to questions about partitions, thresholds, and the resulting anomaly.