Best practice with large databases?

Is there currently any guides that showcases the best-practice when working with complex tables that can span 100k+ rows? What should the architecture look like? Do we split the databases up into several different docs?

1 Like

Coda can “handle” 100k rows but if you by mistake Create a view or something linked to that base table… you risk to end up with a doc that will stay in a crash loop.

1 Like

There are some packs that may help with that, including one for Snowflake. I have not tried them, so do not know how they work, and what they cost.

1 Like