# Multi-batch vs single-batch checkpoints

**URL:** <https://discourse.greatexpectations.io/t/multi-batch-vs-single-batch-checkpoints/665>\
**Category:** Archive\
**Created:** [March 12, 2021, 1:09am UTC](https://discourse.greatexpectations.io/t/multi-batch-vs-single-batch-checkpoints/665 "2021-03-12T01:09:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![wllgrnt](https://avatars.discourse-cdn.com/v4/letter/w/e8c25b/32.png) [@wllgrnt](https://discourse.greatexpectations.io/u/wllgrnt)\
**Post date:** [March 12, 2021, 1:09am UTC](https://discourse.greatexpectations.io/t/multi-batch-vs-single-batch-checkpoints/665/1 "2021-03-12T01:09:02Z")

</div>

(Posted in Slack, reposting here)

If I want to test all of my tables, each of which has an expectation suite associated with it, is it better to use a single checkpoint with multiple batches, or a checkpoint for each table-expectation pair?

My current approach is to have a single checkpoint covering every table in dev, and ditto for prod. I was wondering if there are tradeoffs or disadvantages here that I’m not aware of?

---

<div class="post-metadata">

**Author:** ![eugene.mandel](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.greatexpectations.io/eugene.mandel/32/22_2.png) [@eugene.mandel](https://discourse.greatexpectations.io/u/eugene.mandel)\
**Post date:** [March 22, 2021, 4:20pm UTC](https://discourse.greatexpectations.io/t/multi-batch-vs-single-batch-checkpoints/665/2 "2021-03-22T16:20:42Z")

</div>

@wllgrnt If you have an Expectation in one Suite that uses an Evaluation Parameters whose value is populated from a Validation Result from another suite, these two batches must be validated within the same Checkpoint. In all other cases, there is no clear better option as it depends on your workflow.