AppSheet suddenly cannot see tables in SQL database in azure

[PhilTeare]

We use Google AppSheet, with the data in a SQL database on microsoft azure. A strange issue just appeared today. AppSheet can connect to the SQL Database, but cannot see any views or tables within.

This app has been running for about 2 years, and we've not made any changes recently.

I don't think this issue is anything to do with my specific app / specific SQL database or data within.

To fully test this, I have:

1. Made new credentials for the SQL server access. I've tested them via SSMS, and I can access everything as expected including seeing all the tables / views

2. Made a new data source connection
This tests the credentials & database name - it says all's working & it can connect to the database

3. Made a brand new app

4. Tried to add a datasource from this new app, using these new credentials, to a different SQL database (not the one from my original issue)

I see exactly the same issue - The connection setup says the credentials work, but then it cannot see any tables / views within the database. 

Is anyone else getting this problem at the moment? I'm wondering if AppSheet has rolled an update that's affected these data connections somehow? Any other ideas what I can test or do to fix it?

Thank you.

[rbucsis]

Seems to be a problem going around for everyone. I'm using Postgres and same thing, can't see any tables or views anymore. Also massive performance issues that make apps that were fine last night suddenly not runnable as of this morning. Already sent a support email myself, hopefully something can get done fast.

[PhilTeare]

I very much appreciate the reply - if it's common then my setup is not the common denominator, it'll save me spending the weekend checking SQL server settings.

I have contacted support now too.

[Steve · Accepted solution]

An official response: https://www.googlecloudcommunity.com/gc/AppSheet-Q-A/Bug-Adding-tables-form-MySQL-database/m-p/83734...

[PhilTeare]

thanks, the fixed they've rolled out has fixed it for my app. Phew! thanks everyone.