Skip to content

Temporary removing limits for tables and databases - they are not yet implemented #3156

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jan 29, 2025
Merged

Temporary removing limits for tables and databases - they are not yet implemented #3156

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5af2bcb
Temporary removing limits for tables and databases - they are not yet…
max-vostrikov Jan 28, 2025
7bf7e1a
Trigger DocsBuild
Blargian Jan 28, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions docs/en/cloud/bestpractices/usagelimits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,12 +12,6 @@ Clickhouse is very fast and reliable, but any database has its limits. For examp
If you've reached one of those limits, it may mean that you are implementing your use case in an unoptimized way. You can contact our support so we can help you refine your use case to avoid going through the limits or to increase the limits in a guided way.
:::

# Tables
Clickhouse Cloud have a limit of **5000** tables per instance

# Databases
Clickhouse Cloud have a limit of **1000** databases per instance

# Partitions
Clickhouse Cloud have a limit of **50000** [partitions](https://clickhouse.com/docs/en/engines/table-engines/mergetree-family/custom-partitioning-key) per instance

Expand Down