We are having an issue with metabase not recognizing the datatype of most columns. In admin settings, we are not able to change them to the correct type. So for numbers, we cannot perform calculations.
What version of Metabase are you using?
What database are you using?
What does it say the datatype is, and what should it be?
We are using version 0.57.3
It’s a Microsoft SQL Server database.
Numbers and dates are the big issue because we cannot use any of the metabase features. it recognizes them as ‘No semantic type’ and you can only change them to ‘Category’.
Syn-fks and fingerprint-fields seem to be failing on the sync.
What version of SQL Server?
This is probably the issue. Make sure the Metabase database user can SELECT from the tables. What errors are being logged when you run a sync on this database?
You can also have this problem if you are using domains or user-defined types, as Metabase doesn’t know what to do with those and treats them as opaque values. You can work around this by using a view to cast the values to base SQL types (integer, etc.).
It looks like I might need to migrate H2 to PostgreSQL.
This is what happens with Metabase and SQL Server when sync and fingerprinting don't work. once that breaks, fields fall back to “No semantic type” and you lose numeric/date features.
First, check a few things:
Metabase DB user needs proper SELECT rights, inclu
ding system metadata
watch logs during fingerprint-fields; permission errors usually show up there
if you’re using user-defined types or domains, Metabase can’t infer them — use views to cast to base SQL types
migrating off H2 to Postgres is still a good idea, but it won’t fix typing unless permissions and data types are cleaned up first.