Considering the article on
https://www.googlecloudcommunity.com/gc/Announcements/Announcing-AppSheet-database-General-Availabil...
with:
AppSheet Core | Each user is entitled to: 2,500 rows/database and 10 databases |
Now, I have a workspace standard subscription so with a appsheet core and I have tried to build a test db in appsheet database, I have created a test table with 10k rows...
The limit is exceeded for only 1 table, so I'm a little confused... isn't the limit 2500 rows/database?
Thanks in advance for clarification
Please check this topic.. https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/Rows-per-database/m-p/690337
From the topic it appears that the limit is 2500 rows, but as you can see from the screen, I reached 10000 rows, so we are a bit confusing… the app will work with these database or not?
maybe the tables can exceed the 2500 limit (see the screen) but apps will only handle 2500 rows? we're all a little confused
I have seen this somewhere by a staff member, but yes strange i see you have 9k+ in one table
@Espegg wrote:From the topic it appears that the limit is 2500 rows, but as you can see from the screen, I reached 10000 rows, so we are a bit confusing… the app will work with these database or not?
maybe the tables can exceed the 2500 limit (see the screen) but apps will only handle 2500 rows? we're all a little confused
We chose rows/database as the unit of measurement for pricing because we wanted to give database editors flexibility in use- as long as it's in line with the technical limits. For some plans, users may not hit the technical limitation on the number of rows a table can have in which case it's up to them how to distribute rows across tables.
1) For Core plans, each database can have a max of 2,500 rows. The database editors can decide how to split that up. For example, there could be one table with 2,500 rows (this is well below the technical limitation) or there could be 5 tables with 500 rows. Rows per table is calculated by counting the number of rows in a table.
Alternatively, if a user had an AppSheet Enterprise plan they would be entitled to 200,000 rows/database. However, they would not be able to put all 200,000 rows into one table because that exceeds the technical limit.
2) Answer is similar to the first question: 2,500 rows per DB . Rows per DB is calculated by counting the number of rows across all tables in a database.
3) The database editor can have as many tables as they would like as long as it is lower than the technical limit of 20.
Hi @Hussein_Osseily @AleksiAlkio
thanks for your reply.
In any case today it is not clear if we could use or not more than 2500 rows.
Considering that I have tried with 20k/table rows and the table works anyway...
So today it is not clear if this limitation exist or not.
Anyway we hope to start for all core plan from among 50k for table in order to work properly as the other app platform cause a db with the limit of 2500 rows is useless...
With the Core the limitation is 2500 totally rows in your database. If it works with more than that, it only means the limitation is not set properly.. but it will be. The 50k is just a technical limitation and it doesn't have anything to do with the Core subscription.
If I remember, the limitation is not set completely yet.
User | Count |
---|---|
18 | |
15 | |
10 | |
7 | |
4 |