Changing backend of apps from gsheets to MySQL

[Pratyay_Rakshit]

Our apps have been running off of google sheets for a while now and most of them being very large apps, have collected an enormous amount of data, which is now causing considerable slowing down of the apps.

I know there's a general suggestion for alleviation of this problem - 'archiving' , but I can not do that because of policies too complex and pointless to describe here.

The only option now is to migrate the app to a mysql (or other appropriate databases; I'm open to suggestions) database.

There is documentation on how to do it.

That being only a simplified approach, I would first now ask that what happens to the countless expressions that have been written into the app? Do they remain in place or do I have to rewrite them?

I will ask further questions in the discussion.

[Aurelien]

Hi @Pratyay_Rakshit 

---

@Pratyay_Rakshit wrote:

hat being only a simplified approach, I would first now ask that what happens to the countless expressions that have been written into the app? Do they remain in place or do I have to rewrite them?

---

I'm not sure what you mean with "countless expression". Changing datasource should have not effect.

if your question is about "countless data", then I confirm there is no impact. Otherwise, can you please elaborate?

[Pratyay_Rakshit]

I mean the appsheet expressions that I have written into the columns.

Will they also get transferred as they are?

[Aurelien]

---

@Pratyay_Rakshit wrote:

I mean the appsheet expressions that I have written into the columns.

---

If you talk about those you wrote there:

Then yes.

[Pratyay_Rakshit]

Okay, one ticked.

And all the other workflow stuff like email with PDF attachments, notifications - they would get seamlessly integrated too without further work from my end?

[Aurelien]

Normally yes.

If you are fully using Google Workspace/Sheets/Drive for your app, then what actually matters is:

- default app folder

- documentID of your templates

Again, this is just a database change. Nothing should be impacted.

One thing that could be impacted nonetheless, is the licence price (Enterprise Plan required when using a cloud database)

Also, the database configuration could impact your app in specific cases such as data type, because Google Sheets allow more permissive data entries. If you are familiar with cloud dabatase, you may already be aware of it.

[Pratyay_Rakshit]

Thank you. Some more to know.

The most important - I am not very proficient / familiar with databases, so for further changes and additions I would like to do that in the google sheets and then incorporate them in the app with the database. Can that be done?

[Aurelien]

---

@Pratyay_Rakshit wrote:

for further changes and additions I would like to do that in the google sheets and then incorporate them in the app with the database

---

That's an excellent question.

I would go with a direct work on database, rather than using Google Sheets and applying changes afterward to your cloud dabatase, but it's entirely up to you.

---

@Pratyay_Rakshit wrote:

- I am not very proficient / familiar with databases

---

You may want to give a try with AppSheet Database, though I didn't tested it really myself.

Here is official documentation from AppSheet: 

AppSheet databases - AppSheet Help

Restrictions, limits, and known issues - AppSheet Help

Here is an interesting post from community:

Solved: Pros and Cons of using Appsheet Databases - Google Cloud Community

Depending on your needs, it could fit your expectations.