Limits

A limit is the most of something your workspace can have. It is not a price. At a limit sanda pauses loading or slows queries, and it never bills past one. Prices are on How billing works.

A trial has Standard's limits, with a smaller allowance for sanda search. See Free trial.

How limits work

Edition limits are ceilings. They are the most a warehouse can be set to. You can set any warehouse's limits lower, which is a way to cap a month, and never higher than your edition allows. If you move to a lower edition, sanda caps what you had set at the new numbers.

sanda measures and enforces them itself. It reads each warehouse's size and the work it does regularly, warns at 80% of a limit, and enforces at the limit. Reads, reports and chat keep working throughout.

You are told. When a warehouse passes 80% of a limit, and when it reaches one, sanda emails your owners and admins, unless you have turned those alerts off. The warehouse card also says where it stands. See Budgets and AI limits.

To see or lower a warehouse's limits, go to Data · Warehouse and press Limits on its card. The form has Storage limit (GB), Compute limit (hours/day), Concurrent queries and Statement ceiling (ms). Press Apply limits to save. Only owners and admins can.

Warehouses per workspace

How many warehouses the workspace can hold. The sample learning dataset does not count.

• At the limit, sanda will not provision another. The message names your edition and how many it holds, and says to delete one you no longer need or to move up an edition.
• To raise it, change edition. Beyond the top edition's figure, talk to sanda support.

Storage per warehouse

The most data one warehouse can hold, measured as the size of the warehouse's database. It includes tables you sync or upload, tables and views you build, and sanda search indexes.

• At 80%, the warehouse card reads "Past 80% of a limit".
• At the limit, loading pauses: syncs and CSV uploads stop landing rows. sanda will not start a new search service, because an index needs room to write. Queries are narrowed. Reads, reports and chat keep working. The card reads "At a limit", and loading resumes when the warehouse is back under the limit or the limit moves.
• To raise it, change edition. To get back under it, delete data you no longer need.

Compute per warehouse

Compute is the same on every edition. The table shows the most any warehouse can use at once. It is billed on what runs, not on this ceiling.

You can also set a Compute limit (hours/day) on each warehouse, below the platform's ceiling. You are billed the hours used, including any that run once the warehouse is at its limit.

• At the limit, queries are narrowed, with fewer at once and less time for each, and loading pauses until use is back under. Reads, reports and chat keep working.
• It does not change with edition. Setting a lower limit is how you hold compute spend down.

Concurrent connections per warehouse

How many queries can run against a warehouse at the same moment. It is the Concurrent queries field in the Limits form.

• At the limit, more than that cannot run at the same moment.
• To raise it, change edition. Enterprise allows more, as the table shows. You can set it lower.

Longest single query

The longest a single query can run before sanda stops it. It is the Statement ceiling (ms) field in the Limits form, and it is in milliseconds. Rebuilds of views and scheduled runs have their own separate allowance.

• At the limit, the query is cancelled and returns a timeout error. Narrow it with a filter or a derived view.
• To raise it, change edition. Enterprise allows longer queries. You can set it lower.

Search services per workspace

How many sanda search services the workspace can hold. Basic does not include sanda search, so it has none. Enterprise has no limit.

• At the limit, sanda will not create another. The message says how many the edition allows.
• To raise it, remove a service you no longer need, or change edition.

Rows per indexed table

The largest table a single search service can index. sanda estimates the table's size when you create the service.

• Over the limit, sanda refuses to create the service and suggests narrowing the source with a derived view, or talking to sanda about a larger allowance.
• To raise it, change edition. Enterprise has no limit.

Daily AI limit

The most AI spend a workspace can run up in a day. The table shows where it starts and the most owners and admins can set it to. The limit resets at midnight UTC.

• At the limit, AI waits for the reset. Syncs, reports and your data are unaffected.
• To raise it, an owner or admin can set their own limit up to the ceiling, in Budget & alerts under Settings · Plan & budget. For more, ask sanda support. See Budgets and AI limits.

Schedule grid

Schedules start on a fixed grid of 15 minutes. It is the same on every edition and cannot be raised.

What can be raised

To change edition, see Editions.