I have a live application that’s now backended by SoftrDB. The database currently has 9 tables and around 1200 records across them.
I now want to expand the application to bring in a lot more data - around 10,000 records spread across another 9 tables.
Since there isn’t (currently) a way of relating records across databases, should I bring this new data into the current database, or should I use a separate database and use the Softr front end to display related data. The latter solution is messy, but it would let me play with the data away from the live base.
That’s all assuming there isn’t a way to relate records between bases.
Hi @Bitstreams
Good question. You are right that there is currently no way to relate records across separate Softr databases, so this comes down to whether the new tables need to link to your existing data.
If any of the new tables need related record, lookup, or rollup fields pointing back to your existing tables, they need to live in the same database. Splitting them into a separate database would mean you could only display the two datasets side by side in the front end, you would not be able to actually link records between them.
On scale, this should not be a deciding factor either way. Softr Databases handle well into the hundreds of thousands of records depending on plan, so going from around 1,200 to around 11,200 records across 18 tables total is not close to any limit and can be done starting from the Basic plan.
So unless the new data is fully standalone with no need to connect to your existing tables, I would keep it in the same database.