sql database
96 TopicsSQL database in Fabric: how fresh is the OneLake replica, and what doesn't get mirrored?
Hi all, I'm considering SQL database in Fabric as the operational (OLTP) backend for an internal app, and using its automatic replication to OneLake for analytics instead of building a separate ingestion pipeline. My understanding is that data written to the SQL database is automatically replicated to OneLake in Delta format and can be queried through the SQL analytics endpoint, Spark, or Power BI. Before relying on that, I'd like to understand the details. Questions: Freshness: what replication latency do people see in practice between a committed transaction and the data appearing in OneLake? Does it change under heavy write load? Coverage: which tables, columns or data types are not replicated (for example, certain data types, tables without primary keys, or computed columns)? Is there a way to check replication status for each table? Schema changes: what happens to the OneLake copy when I add, drop or alter a column, or rename a table? Does replication continue, or does the table need to be reseeded? Consistency: if a single transaction updates several tables, do they show up in OneLake together, or can analytics queries briefly see a partial state? Capacity cost: does replication use capacity units separately from the database workload, and is there a way to monitor it? Design: for near-real-time reporting, would you query the replica directly, or still build curated tables in a Warehouse or Lakehouse on top of it? Thanks!9Views0likes0CommentsSQL databases in Fabric run as interactive rather than background workloads
One major challenge I've run into with SQL databases in Fabric is that they run as interactive rather than background workloads. Because the database has to stay online, it continuously consumes CUs, which puts real pressure on shared capacity where pipelines, notebooks, and Power BI are competing for the same resources. Today the only isolation option is moving the SQL database into its own workspace on a dedicated capacity, which adds management overhead and cross-workspace friction. It would be great to see item-level capacity assignment or workload isolation for SQL databases within a capacity — or a background/idle classification so an always-on database isn't billed like an active interactive workload. Is anything like this on the roadmap?Solved137Views1like3Comments[SQL database in Fabric] Saved queries not listed in "My queries" in the query editor (auto-save suc
Product: SQL database in Fabric (NOT Azure SQL Database, NOT Fabric Warehouse) In the query editor of a SQL database in Fabric item, saved queries do not appear under Explorer > Queries > My queries. The queries ARE being saved. Evidence: - New query names keep incrementing (currently at "SQL query 10") - Saving with an existing query name returns a duplicate name error So this is a display/listing issue, not a save failure. Already ruled out: - Cache / cookies / extensions: reproduced in an InPrivate window - Account or profile mismatch: same work account throughout, never switched browser profiles - Environment-wide problem: in the SAME workspace, the SQL analytics endpoint of a lakehouse lists its saved queries under "My queries" correctly. Only the SQL database in Fabric item is affected. Docs for the SQL database in Fabric query editor state that queries are automatically saved every few seconds, with a "saving" indicator in the query tab. The save behavior matches the docs - only the listing is missing. https://learn.microsoft.com/en-us/fabric/database/sql/query-editor Environment: - Item type: SQL database in Fabric - Region: Southeast Asia - Capacity: F8 I checked Known Issues (Databases category) and found no matching entry. Has anyone else seen this with SQL database in Fabric?123Views1like2CommentsCopy Job from on prem SQL to Fabric SQL Database Error
Hi there Fabric Experts. I am trying to copy data(using Copyjob) from SQL on prem to fabric SQL database. My connection works just fine and I can connect to the datasource,view the tables, select incremental column and select my Fabric SQL as a destination(the fabric SQL database exists in the same workspace). However when I run the copyjob it fails with the below error: Fabric activity failed. ' Error occured while trying to get FabricSqlConnectionInfo. Please retry later. Detailed Message: 'StatusCode: NotFound, WorkspaceId: myid, ArtifactId: sqlID, Error Code: ItemNotFound, Message: Could not found the requested item,"errorCode":"ItemNotFound","message":"Could not found the requested item"}' '. Note, ids are masked due to security. It seems to not be able to find the Fabric SQL database although it's created and I can select it as my destination on the CopyJob UI. I can also view and query the Fabric SQL database perfectly from the workspace. The Copyjob just does not seem to find it while running. My aim is to use Fabric Translytical Task flows to update data on Fabric SQL based on the inital load. Is this a known issue? Appreciate any help on it. Thanks3KViews2likes7Comments'EDIT_DISTANCE' is not a recognized built-in function name.
I'm using SQL Sever 2025 Dev Edition and study DP-800 from Microsoft learn When try this code SELECT EDIT_DISTANCE('Apple', 'Apel'); I get this error Msg 195, Level 15, State 10, Line 18 'EDIT_DISTANCE' is not a recognized built-in function nameSolved179Views0likes1Comment"Internal Error" when using SQL DB connection in Lookup/Copy Activity as guest user
Since I couldn't find it in the known issues and just stumbled upon it I thought I'd share. When you're connected to Fabric as a guest user, create a SQL DB, create a connection to that SQL DB, and then try to use that connection in a data pipeline for a lookup or copy activity, you will be able to select the connection and a database, but when searching for table metadata it will fail with the very nondescript "Internal Error". Exact same setup but connection created by a "native" user works as expected.2.3KViews1like4CommentsFabric SQL DB critical CI/CD sync issue
I have a SQL DB inside a fabric workspace and I am setting it up for CI/CD using GitHub. But any sync made via the repository fail when syncing to the workspace. Here are the steps I do: The SQL DB was created within the fabric workspace and the SQL DB works fine on fabric service SQL DB is commited to my repo via the worksapce source control pane I make a simple change to a SQL query via git in the repository I update the workspace items based on the repository changes I get this error: SQL Project build failed. The model version 'SqlDbFabric' is not supported. The model version 'SqlDbFabric' is not supported. And even if I don't make any changes to the repo I get the error: The SQL DB was created within the fabric workspace and the SQL DB works fine on fabric service SQL DB is commited to my repo via the worksapce source control pane I create a new blank workspace in fabric I sync the workspace with the same branch from my repo that I commited in step 2, basically getting the items from the repo to the workspace I get this error: SQL Project build failed. The model version 'SqlDbFabric' is not supported. The model version 'SqlDbFabric' is not supported. Is fabric not cabaple of rebuilding the SQL DB from its own created files? Because the documentation says otherwise. Here is the .sqlproj code autogenerated by fabric: <?xml version="1.0" encoding="utf-8"?> <Project DefaultTargets="Build"> <Sdk Name="Microsoft.Build.Sql" Version="2.1.0" /> <PropertyGroup> <Name>ACTIVITIES_SQL_DB</Name> <ProjectGuid>{00000000-0000-0000-0000-000000000000}</ProjectGuid> <DSP>Microsoft.Data.Tools.Schema.Sql.SqlDbFabricDatabaseSchemaProvider</DSP> <ModelCollation>1033, CI</ModelCollation> </PropertyGroup> <ItemGroup> <PackageReference Include="Microsoft.SqlServer.Dacpacs.DbFabric"> <SuppressMissingDependenciesErrors>False</SuppressMissingDependenciesErrors> <DatabaseVariableLiteralValue>master</DatabaseVariableLiteralValue> <Version>170.0.0</Version> </PackageReference> </ItemGroup> <Target Name="BeforeBuild"> <Delete Files="$(BaseIntermediateOutputPath)\project.assets.json" /> </Target> </Project>1.1KViews1like3CommentsA Typo about View in the explorer of Fabric SQL Database (Korean)
Hi Team, When I am working with views in the Fabric SQL database, I found a typo in the left explorer regarding views: “보기” We can see the “뷰”(View) in SQL Server Management Studio(SSMS). It is also labeled as “뷰”(View) in the template menu. That should be “뷰”. Korean English Thanks, HongSolved2.2KViews1like3Comments