From 0e45761696f8bc153e56568a3da18c20c1aba378 Mon Sep 17 00:00:00 2001 From: "Anna Hoffman (Thomas)" Date: Tue, 2 Sep 2025 11:17:18 -0400 Subject: [PATCH] Enabling is done by default now Removed the instruction for enabling SQL database in Fabric from the write-back scenarios recommendation. --- powerbi-docs/create-reports/translytical-task-flow-overview.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/powerbi-docs/create-reports/translytical-task-flow-overview.md b/powerbi-docs/create-reports/translytical-task-flow-overview.md index 8f49325526..3556651c9e 100644 --- a/powerbi-docs/create-reports/translytical-task-flow-overview.md +++ b/powerbi-docs/create-reports/translytical-task-flow-overview.md @@ -50,7 +50,7 @@ For data write-back scenarios, user data functions have native connection manage * Fabric warehouses * Fabric lakehouses (for files) -For most write-back scenarios, we recommend using SQL database as your underlying data source. SQL databases perform well with the heavy read/write operations required in reporting scenarios. To use a SQL database, a tenant admin needs to [Enable SQL database in Fabric using admin portal tenant settings](/fabric/database/sql/enable). +For most write-back scenarios, we recommend using SQL database as your underlying data source. SQL databases perform well with the heavy read/write operations required in reporting scenarios. For working samples of user data functions, see [Translytical task flow examples](https://gist.github.com/Sujata994/c354ec8d0821e875e45c86f2bd1d5cc8).