Currently the only method of authentication in Fabric pipeline connections to Fabric SQL databases is using OAUTH2, meaning that the credentials of a specific user need to be used (with all the attendant issues around user/credential expiry). By allowing the option of workspace identity for authentication, no user creds would be needed.  Obviously correct access controls would need to be defined, but that's standard SQL Server maintenance. ... 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

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

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

When provisioning a new Fabric SQL Database, after typing in the name I want, what I get is that name PLUS some random GUID characters. This just seems wrong. Nobody likes to have their stuff renamed. As I understand it by someone from Microsoft in the Fabric Community, this was done to ensure a unique name across the entirety of Microsoft Fabric. It would be nice if that was NOT a requirement. Maybe you can make it like Fabric Warehouses where it is the combination of the Tenant, Workspace, and Data Warehouse name that needs to be unique. ... View more

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

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

We are working on a migration project to Fabric and need to combine data from inside a SQL Database with data in a Lakehouse then write it to another table in the database. Due to T-SQL compatibility issue with Data Warehouse, we want to use a Fabric SQL database for the Gold layer. For example: SELECT * FROM SilverLakehouseDeltaTable x JOIN GoldDatabaseSQLTable y ON y.id = x.id   This should be part of a INSERT / UPDATE or MERGE such as:   INSERT INTO AnotherGoldDatabaseSQLTable (Columns) SELECT * FROM SilverLakehouseDeltaTable x JOIN GoldDatabaseSQLTable y ON y.id = x.id The ability to read data from OneLake in a Fabric SQL database would solve this problem. ... View more

When we connect to the DB we have to enter the Database Name  whgich is a GUID. Please make this database name equal to the same name as trhe SQL End Point and database name in Fabric. This imporves usability, and allows for the same 3 part TSQL to run on SQL DB v SQL End Point. At the moment we have different TSQL Statements if we query SQLDB v SQL End Point which is not optimum   ... View more

When doing restore we always get a new database ID, Physical Name and SqlEndPoint, even if the database logical name is the same (eg restore over the top). This causes a massive increase in RTO as afer the restore all end points broke and configuration management had to be updated and re-tested. When doing a restore we need to have the ability to keep database exactly as it was, rather than always creating a clone. In a recent DR event it was 5 minutes to restore, but the 2 days before we stopped getting issues on end points and config change impact. ... View more

It should be possible to query data in a Fabric Lakehouse directly in Fabric SQL database using T-SQL. For example I have the following scenario where I want to join data from a table in my Fabric SQL DB to a delta table in my lakehouse then insert the resultset into another table in my Azure SQL database: INSERT INTO AnotherGoldDatabaseSQLTable (Columns) SELECT * FROM SilverLakehouseDeltaTable x JOIN GoldDatabaseSQLTable y ON y.id = x.id This isn't currently possible with Fabric SQL Database. ... View more

The core issue is the inability to directly access Microsoft Fabric SQL Databases from within Fabric Notebooks, despite the availability of JDBC and ODBC connection strings. The built-in notebook authentication token library appears to be missing Fabric SQL as an option. It does not currently appear possible (or at least not documented how) to access a Fabric SQL Server Database from within a Fabric Notebook. I see JDBC and ODBC connection strings, but these don't work apparently because the library to create authentication tokens is missing Fabric SQL as an option. Current Impact 1. Enterprises must create complex workarounds ("Rube Goldberg architectures") to establish basic data flows that leverage SQL Server 2. The platform fails to deliver on its "unified" promise, leading to a loss of faith in the Fabric brand 3. SQL Server's established strengths are not being leveraged effectively, further eroding trust that Fabric can deliver on enterprise data needs Summary This is a critical feature request that highlights a significant gap in Microsoft Fabric's platform integration. The inability to easily access Fabric SQL Databases from Fabric Notebooks undermines the platform's unified vision and creates unnecessary complexity for enterprise users. The request is well-justified, technically feasible, and would bring significant value to the platform. ... 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

There is currently no way to control the scaling of an SQL DB. There should be a way to limit the database from scaling above a certain size. And / or a way to set a fixed cost/size (similar to DTU purchasing model). ... 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

Within Fabric SQL databases you can cross-database query in the warehouse connection. However cross-database querying from one live SQL database to another is not possible. It would be great to have this possibility with 3-part names: select* from [sqldatabase].[dbo].[table_A]  By getting this migrating from on-prem SQL server or an Azure managed instance to Fabric will be easier. ... View more

Tried using Fabric SQL database to hold the metadata tables for metadata driven ingestion.  Fabric SQL Database is not supported as source in stored procedure activity in pipelines.  We need to update log tables in our metadata db by using the stored procedure activity.  Is adding Fabric SQL Database in stored procedure activity on roadmap soon?   Without this option available Fabric SQL database is not a viable option to replace an Azure SQL DB at this time. Please prioritise this option, Fabric SQL database is available in the Data Pipeline lookup activity so hopefully not to much much effort to also add to stored procedure activity.   Thanks ... View more