It would be beneficial to add when creating a connection for Azure SQL Database from Settings > Management and Connection Gateways to have the option of authenticating with Service Principal. Currently the only option for authenticating for the connection is OAuth 2.0 that it acts as user connection. When a CICD devops pipeline is used to deploy (like using Fabric CI CD opensource library), The SP doesn't have access to connection and therefore fails. ... View more

Since the foundational format for one lake is the delta file format, why has no SQL syntax for adding comments to both Tables and Columns within tables.   With Generative AI, it more important than ever to tag tables and columns with descriptions.   Below is the syntax supported by delta files for tables.   COMMENT ON TABLE table_name IS 'your desired comment';'   Below is the syntax supported by delta files for columns.   ALTER TABLE table_name ALTER COLUMN column_name COMMENT 'your desired column comment';   Please see vendors like Snowflake (warehousing) and PostgreSQL (database) that have implemented this syntax.  It is alot cleaner than the stored procedure syntax in Fabric SQL database.  Below is the comment on a table.   EXEC sp_addextendedproperty @name = N'MS_Description', @value = N'This table contains information about library books on loan, including their ID, book ID, member ID, borrow date, due date, and return date.', @level0type = N'SCHEMA', @level0name = N'data_raw', @level1type = N'TABLE', @level1name = N'loans01';   Additionally, a comment on a column. EXEC sp_addextendedproperty @name = N'MS_Description', @value = N'LoanID', @level0type = N'SCHEMA', @level0name = N'data_raw', @level1type = N'TABLE', @level1name = N'loans01', @level2type = N'COLUMN', @level2name = N'The primary key for the loans table.';   ... View more

Hi, it would be great if, when getting a result from a query in the SQL endpoint, it allowed the option to add thousands separators, currency symbols, etc., to make reading the results easier. ... View more

Description: Currently, when replicating tables from a SQL database to the SQL Analytics endpoint in Microsoft Fabric, all tables are included by default. However, not all tables are needed in the analytics endpoint. This creates unnecessary overhead and, in some cases, leads to lock situations in the SQL database during replication for certain tables. Problem: Some tables are not required in the analytics endpoint. Replication of these tables can cause locking issues in the source SQL database. There is no built-in mechanism to exclude specific tables from replication. Proposed Solution: Introduce functionality to exclude specific tables from replication. This should include: Explicit Table Exclusion: Ability to define a list of tables to exclude. Pattern-Based Exclusion: Support for regex-based patterns to exclude tables dynamically. Example: Exclude all tables ending with __b. Regex equivalent: .*__b$ Benefits: Reduces unnecessary replication overhead. Prevents lock situations on source tables. Provides flexibility for administrators to manage replication scope efficiently. ... View more

Our company wanted to migrate their data from an SQL Server database to Fabric. The database we wanted to migrate has a specific collation, in particular it is case sensitive. It would be nice if we could alter the collation of SQL Databases to make migration easier. ... View more

Current situation: When you start viewing previews of your table in SQL Database, you will only see part of the column names, Values and also the preview mouseovers in a cut-off mode and are not able to adjust the windth an the values:     Future Situation: You're able to adjust the width of the column via drag & drop or even adjust it to the max-width of the values with a double click. Values will be displayed with their full length instead of being cut off.   ... View more

What you would like to accomplish: Introduce catalog-level “join groups” in Fabric/SQL to enable multiple columns across different tables (e.g., fact and dimension tables) to share a consistent dictionary encoding for join keys. This would ensure that identical string or UUID values are assigned the same internal integer code, making joins and group-bys on these keys significantly faster and more memory-efficient. DuckDB Feature Request I made: Shared / Common Dictionary Encoding for Join Keys includes more details on the motivation and potential approaches. BigQuery Feature Request I made https://issuetracker.google.com/issues/442600668  One important detail to highlight is that typical dictionary encoding is local to a column or file, so even if two tables both use dictionary-encoded columns (e.g., customer_id as a string), the integer codes won't match between them. This forces the engine to fall back to comparing the original string values during joins, completely negating the performance benefits of encoding. That’s the core issue this proposal aims to address. How this might work: Allow explicit declaration of “join groups” at the dataset or project level, so that specific columns across tables share the same dictionary domain. Example of a possible SQL API: -- Define a join group to align dictionary codes across tables CREATE JOIN GROUP customer_id_group ( fact_customer_daily.customer_id, fact_customer_orders_daily.customer_id ); -- Optionally rebuild or refresh the dictionary ALTER JOIN GROUP customer_id_group REBUILD; Internally, Fabric/SQL would persist and reuse a common dictionary for the grouped columns, ensuring that equivalent string/UUID values map to identical encoded integer IDs across tables and partitions. If applicable, reasons why alternative solutions are not sufficient: Manual mapping tables: Today, teams often maintain surrogate key lookup tables to replace string/UUID identifiers with integer IDs. This adds complexity, operational overhead, and data engineering effort. Per-table dictionary encoding (as in Parquet/ORC): While these formats support dictionaries, they are scoped to row groups or files, and don’t provide cross-table consistency. Other information (workarounds you have tried, documentation consulted, etc): Current practice in many warehouses (includingFabric/SQL) is to maintain mapping tables for surrogate integer keys derived from string or UUID identifiers. While effective, this approach requires extra ETL complexity and maintenance. Implementing catalog-level shared dictionaries inFabric/SQL could provide operational simplicity and significant performance improvements for users with large, join-heavy analytic workloads. That said, I also want to acknowledge that it's entirely possible systems like Fabric/SQL may already be implementing something along these lines internally, and as an external user, I wouldn’t necessarily have visibility into whether or how that’s happening. ... View more

Currently complext type (json, struct) are supported in Onelake endpoint but not in SQL endpoint which prevents these important payload data types to be explored or used in Power BI. In big data world such fields are very common as many data generated through IoT are partially parsed in individual columns and raw json payload is left for future use or as on need basis. Before parquet - we use to store them as MapType which make them easy to further use. Adding this feature will do both - parsing those field easy for end user and also migration of existing data possible. ... View more

In Fabric Data Warehouse I can select multiple queries and delete them in a single operation (hold down CTRL or SHIFT and select the queries I want to delete, then right click and click delete).   However, in Fabric SQL Database it doesn't seem to be possible to select and delete multiple queries this way.   Please make it possible, thanks! ... View more

Hi,   I am looking for the connector to connect database using pyspark notebook in the same Workspace, and unfortunatlly I have not get the right soluction. could you please help me on how can we connect?   Thanks in Advance, Venkat ... View more

We are having issues inititiating the mirrored tables for large tables. There is very little info on the net about removing the timeout. It would be nice if that is not a restriction for seeding new large tables ... View more

Hi, I think it is very importante that the Fabric SQL database workload could support fully Power BI, also with Direct Lake mode, like it happens for a lakehouse or a warehouse. Fabric SQL database should be fully integrated in the Fabric platform. Thanks ... View more

I suggest including the field parameters functionality in Azure Analysis Services,same as what already exists in power bi ... View more

Overtime queries ran on a sql end point in a lake house build up in the my queries folder. They have to be individually deleted which can take a lot of time. There should be a way to delete all or highlight an delete multiple queries  ... View more

When conectint to a Fabric SQLDB in SSMS  its is very difficult as we need to also enter the datbase name  (this is not so for any other SQL Edition)   We request that the default database for users be set the the Fabric SQLDB, so that they do not need to specify the database name in connections   It makes no sense to make master the defautl database if no one is allowed connect to it. ... View more

As an experienced SQL developer, the ability to quickly covert columns to lists greatly improves workflows.   I have developed functions that convert columns to lists that are of much use to me. Further, my column-to-list functions can be set to do a column-to-bracketed list or a column-to-quoted list. That functionality is a game changer.    Simple idea, but I guanrentee that SQL developers will appreciate it. Most do not develop their own column-to-list functions. Instead they often copy and paste lists in excel or 3rd party apps to convert.  ... View more

Currently, if you start a manual refresh for a dataset (Azure SQL in my case), then start a refresh schedule for that dataset before the manual refresh finishes, the refresh schedule will be wiped when the manual refresh finishes (I have reproduced this many times).   This is either a bug, or this feature should be changed. The current behavior of wiping scheduled refreshes makes no sense. ... View more

We want to create Power BI data connection in our on premise gateway server to point to the secondary node of SQL server instead of the primary. But currently there is no way we can put a parameter ApplicationIntent to ReadOnly for same. This feature should be available ... View more