I’m not sure what was the exact cause, but I’ve set up Metabase on our SQL Server, and after a short while it caused the DB to lock down for an hour (our DBA told us the queries came from the Metabase server). What I mean by lock down is that all queries to the DB got stuck.
This draws me to a few questions:
- Do you have any idea if Metabase can cause this directly?
- If query results are too large, can’t Metabase place some timeout on them?
- If I run a query and don’t wait for it, exiting the browser. Does it still load?
- Can I set “READ UNCOMMITTED” transaction isolation level for Metabase? What is currently set?
- One of the queries that possibly locked the DB did a count(*) on a table with a huge number of rows. Can I set a default limit to query sizes?
Many thanks