Using Metabase 0.33.5.1 on Centos connecting to SQL Server 2014
We randomly started getting SQL Server exceptions in the form of “Invalid object name ‘TableName’” where 100% the table exists. Some of these are our main invoice tables etc, there is no doubt that they are there. Our solution generally has been to add to the queries the full [DatabaseName].dbo.TableName which works sometimes, however you cannot use for field filter variables.
Any thoughts? The database name is setup in the connection and it is syncing every night. One minute the question will work, then refresh and the log shows the error. We have seen this on multiple Metabase versions, hoping installing the latest will have a fix.
Thanks in advance.