Add a note/screenshot on using Metabase with the DDN + a partial bug fix for introspection.

Author: mildbyte

content/docs/0700_integrating-splitgraph/0450_metabase.mdx

@@ -8,7 +8,7 @@ allowing you to visualize datasets that were cloned and checked out on the engin
 also works with [layered querying](../large-datasets/layered-querying), letting it query
 huge datasets by only downloading a required fraction of the data.
 
-However, there is currently an issue with Metabase Explore Data view: it doesn't support schemata with slashes in them that Splitgraph uses by default to check data out into. There's an [open GitHub issue](https://github.com/metabase/metabase/issues/12450) for this.
+Make sure to use Metabase version v0.36.8 or above. Earler versions have an [issue](https://github.com/metabase/metabase/issues/12450) with the Metabase Explore Data view: it doesn't support schemata with slashes in them that Splitgraph uses by default to check data out into.
 
 #### Start Metabase
 

content/sql-client-instructions/Metabase.mdx

@@ -1,5 +1,10 @@
 # Metabase
 
-Data discovery (introspection query interception) doesn't work with Metabase, as our `information_schema` implementation returns slashes in schema names. See the [GitHub issue](https://github.com/metabase/metabase/issues/12450) for details.
+You can set up the Splitgraph DDN in Metabase like any other PostgreSQL connection. Make sure to use SSL and disable prepared statements in the Metabase JDBC parameters (`prepareThreshold=0`).
 
-SQL queries work, allowing you to use Splitgraph data in your Metabase dashboards.
+![Metabase settings for setting up the Splitgraph DDN](https://raw.githubusercontent.com/splitgraph/splitgraph.com/master/content/sql-client-instructions/images/metabase-01.png)
+
+Data discovery (introspection query interception) only works in Metabase version v0.36.8 or above. Earler versions have an [issue](https://github.com/metabase/metabase/issues/12450) with slashes in schema names
+that Splitgraph DDN uses to denote repositories.
+
+Note that there are still some outstanding issues with Metabase X-Rays and automatically generated questions on the DDN. You can still use direct SQL queries, allowing you to reference Splitgraph data in your Metabase dashboards.