3459 tables in 90 schemas. (plus another 25 empty schemas)
The 1 schema that is properly showing up has 60 tables in it.
@Luiggi any update or versions for us to try?
nope, nothing, we've been trying by all means with the team and we are running in circles, several people have hit the same but no one was able to provide steps for reproducing this consistently
We have the same issue in our Metabase Cloud setup, I'm going to drop a message to support shortly
In our setup we have multiple virtual databases, they do have slightly different configurations but they're all using the same Snowflake instance and user
Interestingly only one of the virtual databases is having the problem described, I've tried several of the same routes as described by others in the post but to no success. I've dug a little into the logs available via Metabase Cloud and can see that this change happened somewhere between 2024-01-17 23:26:44 and 2024-01-18 00:24:21 (I assume UTC, the logs don't say) because there is a task that returns the number of tables found and I can see that we dropped from 91 to 19 between the two task runs. This does not correspond to anything we've done in Snowflake
Like I say, I'll drop a note to support, but wanted to flag here as well that I've done some investigation on our Metabase Cloud setup and there is potential that it's in a state where we might be able to figure out the problem. I am available to call and help as well as I would like to get this resolved without having to delete and recreate the virtual database (with its questions)
please contact us right away so we can debug this on a video call, thanks
I emailed the help mailbox, got a request number back of 24314. I'm not sure what you get to see in this platform, but the request is on the same email as this account so feel free to email me and we can organise
1 Like
Continuing the discussion from Snowflake broken in 0.48.1:
After our cloud instance was updated to v48 our production database stopped syncing and being queryable- responding with {"updated-tables":0,"total-tables":0} if I check the task view - sync-tables
The exact connection and permission details are used for our staging db and which is still syncing correctly, user role is empty in staging and production db connection settings, the change occurred between 00:31 and 01:31 on the 18th of Jan, a day after we received the update email.
2024-01-18T01:31:03.086233Z it shows 0 tables
2024-01-18T00:31:05.294133Z and before it shows 307 tables
The logs show the it takes 17ms for production to be check for tables to Start and Stop trying to sync.
[a2fec4e0-e95d-44c0-9f77-9a0d4fecc67e] 2024-01-24T12:42:47+02:00 INFO metabase.sync.util STARTING: step 'sync-tables' for snowflake Database 2 'snowflake_ANALYTICS'
[a2fec4e0-e95d-44c0-9f77-9a0d4fecc67e] 2024-01-24T12:42:47+02:00 INFO metabase.sync.sync-metadata.sync-timezone :snowflake database 2 default timezone is "America/Los_Angeles"
[a2fec4e0-e95d-44c0-9f77-9a0d4fecc67e] 2024-01-24T12:42:47+02:00 INFO metabase.sync.util FINISHED: step 'sync-tables' for snowflake Database 2 'snowflake_ANALYTICS' (1.6 ms)
We have followed the guidance given via the update 48 email around permissions but it has not made an impact to the logs or task and the prod db is still not showing any tables.
alright, we think we found the issue, any self hosted user that wants to test it out?
yes we can test it out!
Ok, links are the same as I used above, make sure you pull the image and the JAR again and test it. These binaries are based on version 48
Someone?
it works!!! ship it!!! thank you!!
Will come on Monday
48.4 has been released, it should fix the issues