Hi, I've noticed that T-SQL language of a warehouse doesn't support the recursive CTEs. It'a real pity! A such feature is more useful and comfortable one in several scenarios, f.e. to navigate an hierarchy. I hope it will be implemented as soon as possible. Thanks ... View more

If you try to call interface updateFromGit (https://learn.microsoft.com/en-us/rest/api/fabric/core/git/update-from-git) with a Service Principal you get:    "Error details '{"requestId":"xxx","errorCode":"BadRequest","moreDetails":[{"errorCode":"PrincipalTypeNotSupported","message":"The operation is not supported for the principal type","relatedResource":{"resourceType":"Warehouse"}}],"message":"The request could not be processed due to missing or invalid information"}'" Same for error when you want to call interface deploy-stage-content (https://learn.microsoft.com/en-us/rest/api/fabric/core/deployment-pipelines/list-deployment-pipeline-stages) using a DevOps connection configure with a service principal    This hinders automation for SQL-base deployment in Fabric!    ... View more

Dark Mode for Power BI Service and Fabric. ... View more

During Lakehouse deletion operations in Microsoft Fabric, users may observe that the associated SQL Endpoint and Semantic Model are not automatically removed. These orphaned artifacts may cause downstream deployment errors or stale resource references.   There is one available API to remove it, but it is not very user friendly and also requires admin rights so developers cannot do this on their own. It is mentioned here: Solved: Can't delete orphaned lakehouse SQL analytics endo... - Microsoft Fabric Community   The idea is to make this option available in the UI or at least provide more user friendly ways to do it. ... View more

A Lakehouse Collation setting showing case sensitive vs non-case sensitive should be added to the exisitng lakehouse settings in Microsoft Fabric.  For years i've been able to change collations on a database on on-prem SQL and am able to re-populate those data tables to reflect the new collation moving forward.  This should be an option in Microsoft Fabric in the lakehouse settings which should allow me to change a collation on an existing Lakehouse without having to create a brand new Lakehouse and have to completely recreate anything in it's lineage such as semantic models, reports, etc.  Seems like we could do this for the last 20+ years in SQL and should be able to do this using a Lakehouse easily as well. ... View more

When connecting to a semantic model currently, we have to use the workspace/lakehouse/warehouse unique id and semantic model unique id in order to analyze that semantic model.  Instead of using those unique ids attached to a very specific semantic model we should be able to have the ability to customize those unique ids to a static customizable user friendly names for ease of use and the best customer experience.  Currently if I want to analyze a semantic model in Microsoft Excel or another methodology, if I have to connect to that model with the unique workspace/warehouse/lakehouse id and unique semantic model id, why can't I use the user facing workspace name, lakehouse name and semantic model name?  Why are we using GUIDs in 2025?   Additionally, if I have a new model that needs to replace an existing model, I should be able to replace or rename that model to the existing model name and it should inherit the current model's lineage vs recreating and redeploying all the associated lineage items to the new model.  This would save so much development time it's ridiculous that there is no solution for this currently. ... View more

Currently I need to use Tabular Editor to make modifications to the collation assigned with any semantic models I create in Microsoft Fabric.  These collations appear to be a random bug and do not always inherit my lakehouse collation.  This causes issues when my users/customers try to analyze a semantic model inside of Microsoft Excel and try to filter data for a specific data value in the model that is case sensitive.  A button should be added to the semantic models settings that turns case sensitivity on or off.  As a work around, I am currently using Tabular editor to modify a semantic model and deploy a copy to Fabric.  This does not allow me to modify the existing semantic model, but create a new semantic model with the collation I want.  This should be an easy add/fix that should already be in Microsoft Fabric since it's kind of already in a 3rd party tool. ... View more

I can't see the column names and cell values in some of the columns in my tables in SQL Analytics Endpoint because the column width is too narrow.   Also, the tooltip also doesn't show the entire cell contents when hovering over a cell.   Please make it possible to see the entire contents of a cell in the SQL Analytics Endpoint user interface. ... View more

Hi, it would be much appreciated exporting to Excel the resulting dataset generated by a SQL query executed in the SQL analytics endpoint of a lakehouse. I'm referring to the data and not to the query. Thanks ... View more

The underlying architecture of data warehouse within Microsoft Fabric is Delta/parquet ,but coming from a relational database world ,when we create primary key it is always enforced and helps maintains the consistency in the database /datamart .But Fabric warehouses does not enforce primary key which needs to be addressed . ... View more

The only step in my deployment for test and production switching that is still unsupported are DirectLake semantic model sources. I have been successful in some hacky fixes where I can parameterize the directlake source but it then breaks editing of the directlake semantic models.   Specifically toggling the url in the semantic model expression: expression 'DirectLake - kusa_accounting' = let Source = AzureStorage.DataLake("https://onelake.dfs.fabric.microsoft.com/workspaceid/lakehouseid", [HierarchicalNavigation=true]) in Source   If we could usue a parameter here, normal Deployment Pipeline rules could change this. Better would be detecting this data source and allowing for setting the url in a data source pipeline rule would save having to create a parameter myself.   Alternatively, I'm using Variable Libraries in my other areas of deployment, and if we could specify this url from the Variable Libraries would work. This would probably be better since I find Variable Libraries more flexible and usable even without Fabric Deployment Pipelines. ... View more

Since there is a problem with operation when the account of the owner of the created lakehouse content is closed, I would like to add the function to change the function of the owner ... View more

Could the DDL-support in Warehouse get closer to what we have in Synapse/SQL Server? ALTER COLUMN would be much approciated.   ... View more

Fabric DW currently supports the EOMONTH() function, which returns the last day of a given month. However, it does not provide a built-in function that can return the last day of a week, quarter, or year in addition to the month. Calculating the last day of a week, quarter, or year requires custom expressions using combinations of DATEADD, DATEDIFF, and calendar logic. This adds complexity and reduces readability in time-based reporting and analytics. The LAST_DAY() function is supported in several other databases Snowflake, MySQL, Oracle, and makes calculating the last dat in interval much easier:   LAST_DAY('2025-08-18', 'MONTH')   -- → 2025-08-31 LAST_DAY('2025-08-18', 'QUARTER') -- → 2025-09-30 LAST_DAY('2025-08-18', 'YEAR')    -- → 2025-12-31 LAST_DAY('2025-08-18', 'WEEK')    -- → 2025-08-23   The equivalent expressions in Fabric DW are:   SELECT EOMONTH(DATEADD(QUARTER, DATEDIFF(QUARTER, 0, '2025-08-18'), 0)) AS LastDayOfQuarter; SELECT EOMONTH(DATEFROMPARTS(YEAR('2025-08-18'), 12, 1)) AS LastDayOfYear; SELECT DATEADD(DAY, 7 - DATEPART(WEEKDAY, '2025-08-18'), '2025-08-18') AS LastDayOfWeek; ... View more

Currently the server name for SQLDB (and DW) is a double GUID of {tenant-Id-workspace-id.}database.fabric.microsoft.com   This causes a lot of issues as 1. This is impossible to remember 2. We ahve no way to distinguish test from PRD   We request user frirnedly DNS Names like  Prodata-Sales-DEV.database.fabric.microsoft.com   This would help clearly label an worksapce as DEV or PRD and avoid confusion and make the platform easier to work with., ... View more

Fabric Data Warehouse allows reading Parquet and CSV files using the OPENROWSET function. However, it does not support external tables that reference Parquet or CSV files (CREATE EXTERNAL TABLE (Transact-SQL) - SQL Server | Microsoft Learn). This limitation hinders the straightforward migration of Polybase external tables from Synapse dedicated/serverless pools or SQL Server. The only available workarounds for migration involve either converting Parquet/CSV files to Delta Lake format or rewriting the code to use OPENROWSET, which lacks the same security model. As a result, migrating from Synapse or SQL Server to Fabric Data Warehouse requires data or code conversion.   Supporting external tables with Parquet and CSV files is crucial for seamless migration and ensuring compatibility with other SQL Server/Data Warehouse offerings. ... View more

SQL Server 2025 adds Regex functions support, this is present also in SQL database in Fabric, Azure SQL DB and Azure Managed Instance as per:   https://learn.microsoft.com/en-us/sql/relational-databases/regular-expressions/overview?view=sql-server-ver17   it would be beneficial to have Regex support also in lakehouse and warehouses. ... View more

OPENROWSET function can read the files from Azure Data Lake storage or Azure Blob storage.  It would be useful to enable OPENROWSET to also read files form Fabric One Lake and access the files in Lakehouse /Files area. ... View more

SET QUERY_GOVERNOR_COST_LIMIT feature is available in Fabric SQL Endpoint.  However, the official documentation states that Fabric SQL Endpoint is not supported in the products that support this feature. We want this feature to be added to the official documentation so that it can be used in Fabric SQL Endpoint. SET QUERY_GOVERNOR_COST_LIMIT (Transact-SQL) - SQL Server | Microsoft Learn ... View more