Glide Big Tables - pricing

Ask for Help
41

You need to get yourself on the early access program.

1 Like
42

@Eric_Penn @Darren_Murphy @gvalero we’ve closed the beta for now. Customers on our Business and Enterprise plans will have access to Big Tables. @gvalero if you’d like to test it out you can start a trial of the Business plan. If you don’t see Big Tables as an option please send me a PM.

3 Likes
43

Thanks @Sean_Martin !

44

Read today that big tables use Sycns. what counts as a sync in big tables? is that only when more than 1 app is connected to a big table?

45

Big Tables aren’t loaded in their entirety due to their size. Any time you need to get a different set of data, it will be a sync.

46

has anyone received their glide big tables first bill? would be interesting to get feedback on the cost of using them

47

I’m also wondering about ‘row updates’ and big tables. Let’s say I have a million rows in a Big Table and need to update them (not create new rows). Is that a million updates?

48

It depends how you do it. If you were to use the API, then yes that would be one million updates.
What I would probably do in this case is export the whole lot to CSV, apply a bulk update using a data editor, and then import again. This approach would incur zero updates.

49

We have had huge issues with data import into Glide Big Tables to a level we opted to forget about Glide Big Tables completely 


50

Yes, I remember your issues. You never got a satisfactory response or resolution from Glide Support?

I can’t say that I’ve experienced the same, but the most I’ve ever tested with is a few thousand rows. This will change in the near future, so it’s definitely something I’ll be keeping an eye on.

51

i’m not sure why my post required approval before posting !!

52

Glide was helpful, the community as well a lot. It wasn’t really a tough decision. Glide Tables wasn’t a clear feature for us. Its pricing and usability
 it didn’t even seem like the feature had much support within the community.

Our main aim was to use it to store order history data. Instead we opted to place a backup in an ordinary 2nd app. So now we have loads of backup apps
 once a certain time passes we un publish them. The recent ones, we can check quickly to check an order which is disputed with a client after delivery.

What do you think will change in near future? anything related to Glide Big Tables?

1 Like
53

Interesting. I just approved it. Apparently it contained a “watched word”, although I don’t know which one it was :man_shrugging:

1 Like
54

My understanding is that the longer term goal is to remove the distinction between regular tables and Big Tables. I take that as meaning that we will get all the benefits of Big Tables, but without the current limitations. But I guess we will just have to wait and see :slightly_smiling_face:

1 Like
55

Thanks Darren. Not sure that’s possible, but good to know the options. :pray:

I have some rows with nested item arrays in json.
I’d thought to flatten out my row data structure that has nested arrays of many items to make displaying collection data easier and use Big Tables, but rows are going to mount up fast.

Would be great if glide had a way to loop over nested arrays in a row without needing a collection. Perhaps I’ve missed something. Will do a search as I’m guessing that’s a common issue.

56

Typically how large are these arrays?

The usual approach to this is to use a Helper Table to dynamically unwind the array into a list (eg. one item per row), and then use that in a Collection. This method can work quite effectively with up to a few thousand rows.

2 Likes
57

Thanks Darren, will check that out in the forum as I see it’s been mentioned. It will start at about 60 items and will grow from there to about 100.

I think the better approach may be just to keep data managed outside of Glide (using a Google Cloud database), perform operations there and have that synced in Glide and then to do ‘stuff’ with existing structured data.