diff --git a/_docs/master/developers-guide/driver-changelog.md b/_docs/master/developers-guide/driver-changelog.md
index 440befd6e9..c0cf5b4c02 100644
--- a/_docs/master/developers-guide/driver-changelog.md
+++ b/_docs/master/developers-guide/driver-changelog.md
@@ -19,11 +19,18 @@ layout: new-docs
   longer include parent column names for drivers like MongoDB -- use `qp.add.nfc-path` instead to qualify the
   `qp.add.source-column-alias` with parent column names as needed.
 
+## Metabase 0.56.3
+
 - Added metabase.driver/compile-transform, metabase.driver/compile-drop-table, metabase.driver/execute-raw-queries!,
   metabase.driver/run-transform!, metabase.driver/drop-transform-target!, metabase.driver/native-query-deps,
   metabase.driver/connection-details, metabase.driver/table-exists?, metabase.driver.sql/normalize-name,
   metabase.driver.sql/default-schema, and metabase.driver.sql/find-table to implement sql transforms.
 
+- Added the driver multi-method `driver/describe-database*` that drivers should now implement instead of `driver/describe-database`.
+  This provides automatic resilient connection handling for better error recovery when database connections are closed
+  during metadata sync operations. Existing drivers implementing `describe-database` will continue to work but should
+  migrate to `describe-database*` to benefit from the resilient connection handling.
+
 ## Metabase 0.56.0
 
 - Add the testing multi-method `tx/track-dataset` for shared cloud dbs to track loaded datasets for more efficient sharing.
diff --git a/_docs/master/questions/native-editor/writing-sql.md b/_docs/master/questions/native-editor/writing-sql.md
index e1730755b2..ac51c3e0c8 100644
--- a/_docs/master/questions/native-editor/writing-sql.md
+++ b/_docs/master/questions/native-editor/writing-sql.md
@@ -99,6 +99,16 @@ You can use [Snippets](snippets) to save, reuse, and share SQL code across multi
 
 When you run a query from the SQL editor, Metabase sends the query to your database exactly as it is written. Any results or errors displayed in Metabase are the same as the results or errors that you would get if you ran the query directly against your database. If the SQL syntax of your query doesn’t match the SQL dialect used by your database, your database won’t be able to run the query.
 
+## The native query editor is designed for reading data, not writing it
+
+The native SQL editor is designed for asking questions about your data. Don't use the editor for:
+
+- Multi-statement queries
+- Stored procedures and function calls
+- DDL statements (like `CREATE`, `ALTER`, or `DROP`)
+
+Depending on your connection's privileges, some of the above actions may work, but none are officially supported, and we recommend against using the native query editor for these tasks.
+
 ## Question version history
 
 For questions, [dashboards](../../dashboards/start), and [models](../../data-modeling/models), Metabase keeps a version history for the previous fifteen versions of that item.
diff --git a/_site/docs/master/developers-guide/driver-changelog.html b/_site/docs/master/developers-guide/driver-changelog.html
index 3d340f909e..1543fdb9f8 100644
--- a/_site/docs/master/developers-guide/driver-changelog.html
+++ b/_site/docs/master/developers-guide/driver-changelog.html
@@ -4874,12 +4874,23 @@ <h2 id="metabase-0570">Metabase 0.57.0</h2>
 longer include parent column names for drivers like MongoDB – use <code class="language-plaintext highlighter-rouge">qp.add.nfc-path</code> instead to qualify the
 <code class="language-plaintext highlighter-rouge">qp.add.source-column-alias</code> with parent column names as needed.</p>
   </li>
+</ul>
+
+<h2 id="metabase-0563">Metabase 0.56.3</h2>
+
+<ul>
   <li>
     <p>Added metabase.driver/compile-transform, metabase.driver/compile-drop-table, metabase.driver/execute-raw-queries!,
 metabase.driver/run-transform!, metabase.driver/drop-transform-target!, metabase.driver/native-query-deps,
 metabase.driver/connection-details, metabase.driver/table-exists?, metabase.driver.sql/normalize-name,
 metabase.driver.sql/default-schema, and metabase.driver.sql/find-table to implement sql transforms.</p>
   </li>
+  <li>
+    <p>Added the driver multi-method <code class="language-plaintext highlighter-rouge">driver/describe-database*</code> that drivers should now implement instead of <code class="language-plaintext highlighter-rouge">driver/describe-database</code>.
+This provides automatic resilient connection handling for better error recovery when database connections are closed
+during metadata sync operations. Existing drivers implementing <code class="language-plaintext highlighter-rouge">describe-database</code> will continue to work but should
+migrate to <code class="language-plaintext highlighter-rouge">describe-database*</code> to benefit from the resilient connection handling.</p>
+  </li>
 </ul>
 
 <h2 id="metabase-0560">Metabase 0.56.0</h2>
diff --git a/_site/docs/master/questions/native-editor/writing-sql.html b/_site/docs/master/questions/native-editor/writing-sql.html
index 0ddd5e3071..2f093c6c93 100644
--- a/_site/docs/master/questions/native-editor/writing-sql.html
+++ b/_site/docs/master/questions/native-editor/writing-sql.html
@@ -4945,6 +4945,18 @@ <h2 id="how-metabase-executes-sql-queries">How Metabase executes SQL queries</h2
 
 <p>When you run a query from the SQL editor, Metabase sends the query to your database exactly as it is written. Any results or errors displayed in Metabase are the same as the results or errors that you would get if you ran the query directly against your database. If the SQL syntax of your query doesn’t match the SQL dialect used by your database, your database won’t be able to run the query.</p>
 
+<h2 id="the-native-query-editor-is-designed-for-reading-data-not-writing-it">The native query editor is designed for reading data, not writing it</h2>
+
+<p>The native SQL editor is designed for asking questions about your data. Don’t use the editor for:</p>
+
+<ul>
+  <li>Multi-statement queries</li>
+  <li>Stored procedures and function calls</li>
+  <li>DDL statements (like <code class="language-plaintext highlighter-rouge">CREATE</code>, <code class="language-plaintext highlighter-rouge">ALTER</code>, or <code class="language-plaintext highlighter-rouge">DROP</code>)</li>
+</ul>
+
+<p>Depending on your connection’s privileges, some of the above actions may work, but none are officially supported, and we recommend against using the native query editor for these tasks.</p>
+
 <h2 id="question-version-history">Question version history</h2>
 
 <p>For questions, <a href="../../dashboards/start">dashboards</a>, and <a href="../../data-modeling/models">models</a>, Metabase keeps a version history for the previous fifteen versions of that item.</p>