From b42d8b55a2681f9488942be6e2176f8619e96215 Mon Sep 17 00:00:00 2001
From: Colton Padden <colton@dagsterlabs.com>
Date: Fri, 20 Dec 2024 09:34:45 -0500
Subject: [PATCH] [docs] add note of defer_table_reflect to dlt docs

---
 docs/content/integrations/embedded-elt/dlt.mdx | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/docs/content/integrations/embedded-elt/dlt.mdx b/docs/content/integrations/embedded-elt/dlt.mdx
index fb9f62066834b..b81e9c551b53f 100644
--- a/docs/content/integrations/embedded-elt/dlt.mdx
+++ b/docs/content/integrations/embedded-elt/dlt.mdx
@@ -183,6 +183,16 @@ The <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator />
 
 In the same file containing your Dagster assets, you can create an instance of your <PyObject object="dlt_assets" module="dagster_embedded_elt.dlt" decorator /> by doing something like the following:
 
+<Note>
+  If you are using the{" "}
+  <a href="https://dlthub.com/docs/api_reference/sources/sql_database/__init__#sql_database">
+    sql_database
+  </a>{" "}
+  source, consider setting <code>defer_table_reflect=True</code> to reduce
+  database reads. By default, the Dagster daemon will refresh definitions
+  roughly every minute, which will query the database for resource definitions.
+</Note>
+
 ```python
 from dagster import AssetExecutionContext, Definitions
 from dagster_embedded_elt.dlt import DagsterDltResource, dlt_assets