<@U04S8PLJWMT> GIVE ME THE DOCUMENTATION TO INCREA...
# ask-ai
s
@kapa.ai GIVE ME THE DOCUMENTATION TO INCREASE NUMBER OF TABLES BEING INGESTED ITS LIKE 25 TABLES ARE BEING INGESTED AND AFTER 25 REMAINING ARE NOT GETTING STARTED WHATS THE REASON
k
Airbyte doesn’t expose a single “max tables per sync” knob, but the behavior you describe (only ~25 tables progressing, others not starting) matches known limits around: 1. Per‑connection table count / stream concurrency - For some CDC scenarios (e.g., Postgres → Snowflake), Airbyte internally limits concurrent buffered streams (e.g., 10 by default for Snowflake). With many tables, this can severely slow or block progress for the rest. The workaround recommended by Airbyte support is to limit the number of tables per connection (e.g., max ~30 tables) and split into multiple connections. [[Postgres CDC issue](https://discuss.airbyte.io/t/4373); [Snowflake table-count issue](https://discuss.airbyte.io/t/2119)] 2. Message size / catalog size limits - When a connection has too many tables or very wide schemas, you can hit gRPC/message-size limits or UI/rendering limits. This has been observed around hundreds to thousands of tables, especially above ~250–6000 tables depending on connector and setup. In these cases, discovery or sync may silently fail or partially work, and the recommended workaround is again to split tables into multiple connections. [[Table limit 250+](https://discuss.airbyte.io/t/2119); [6000-table limit](https://discuss.airbyte.io/t/84); [Oracle 13k tables error](https://discuss.airbyte.io/t/1811)] There is no documented setting to simply “increase the maximum number of tables per connection” beyond these internal/message-size constraints in the provided docs. What you can do: 1. Split tables into multiple connections - Group your tables (e.g., 20–30 per connection, especially for CDC or very wide tables) and create multiple Airbyte connections rather than one huge connection. [[Postgres CDC issue](https://discuss.airbyte.io/t/4373); [Snowflake table-count issue](https://discuss.airbyte.io/t/2119)] 2. Ensure you have enough concurrent workers (if you are on Enterprise / Helm) If the issue is that jobs are queued and not starting (vs. failing), check the concurrent worker limits and worker replicas:
Copy code
yaml    # Helm chart V1    worker:      extraEnv:        - name: MAX_SYNC_WORKERS          value: "5"      # increase if you need more concurrent syncs        - name: MAX_CHECK_WORKERS          value: "5"      replicaCount: 2     # increase replicas for more workers
Copy code
yaml    # Helm chart V2    worker:      maxSyncWorkers: 5    # increase as needed      maxCheckWorkers: 5      replicaCount: 2
[[Scaling Enterprise](https://docs.airbyte.com/platform/enterprise-setup/scaling-airbyte)] If you can share: source connector, destination connector, deployment type (Docker vs Kubernetes/Helm), and roughly how many tables you selected on that connection, I can point you to the most relevant specific workaround from these docs.