You have connected Metabase to a database, but:
If you can see the tables, but some of the rows or columns seem to be missing, please check out the troubleshooting guide for sandboxing.
Root cause: Sometimes browsers will show an old cached list of tables.
Steps to take: Refresh your browser tab and check for your table or tables again.
Root cause: The database doesn’t exist. For example, you may have connected to a test database while doing an evaluation but are now in a production environment.
Steps to take:
Exactly what settings you need will depend on your environment. To test that the settings are correct:
If you can’t connect to the database with another application, the problem is probably not with Metabase. Please check that the database server is running and that you have the correct host, port, username, password, and other settings.
Root cause: The table you think you should be able to see does not exist (e.g., it has a different name than you expect).
Steps to take: To test that the table you are trying to query actually exists and that you have permission to access it, use the SQL Editor to create and run a query like:
select * from SOMEWHERE
where SOMEWHERE is the table you think you should be able to see. Metabase should display an error message like:
Table "SOMEWHERE" not found
If you see this message, use another application (e.g., psql for PostreSQL) to send the same query to the database. If it also produces a “table not found” message, check the database schema and the spelling of the table name.
Be sure to log in using the same credentials that Metabase uses. A common source of problems is that the Metabase “user” does not have the same privileges as a member of IT staff or a developer, so tables that are visible to the latter using external applications are not visible to Metabase.
Root cause: The login ID that Metabase uses to query the database doesn’t have privileges to view the table.
Steps to take: Use the SQL Editor to write and run a simple query like the one shown immediately above:
where SOMEWHERE is the table you think you should be able to see. If Metabase produces an error message saying the table can’t be found, run the same query using another application. Again, make sure to log in using the same credentails that Metabase uses, not your regular account.
Root cause: Metabase uses a group-based permission model: people belong to groups, and administrators can set permissions so that some groups cannot see all of the tables. (It also allows administrators to control which rows or columns specific people can see—issues with that are covered in the troubleshooting guide for sandboxing.)
If the administrator’s account can see the tables but an individual person cannot:
Root cause: In order to display available tables and columns in dropdown menus and previews, Metabase runs a query every hour to find out what tables are available and what columns are in each available table, and stores this information in its application database.
Did this article help you?
Thanks for your feedback!