Skip to main content
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Get Fabric Certified for FREE during Fabric Data Days. Don't miss your chance! Request now

Share your ideas and vote for future features

Suggest an idea
BobDuffyIRL

SQLDB and DW and LH - Allow friendly server Name (DNS)

Submitted on ‎03-19-2025 02:53 AM Submitted by on ‎03-19-2025 02:53 AM
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
Status: Under Review

Thanks @BobDuffyIRL , We are reviewing this feedback and considering for development and design in our planning cycle. Please stay tuned, this planning work is under progress

See more ideas labeled with:
3 Comments (3 New)
todd_chittenden

Fabric SQL Database names: Remove GUID suffix

Submitted on ‎12-09-2024 06:18 AM Submitted by on ‎12-09-2024 06:18 AM
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
Status: Planned

We do plan to remove the GUID from the database name/url

See more ideas labeled with:
2 Comments (2 New)
higgy7

Method to bulk delete sql endpoint queries

Submitted on ‎04-22-2025 10:55 AM Submitted by Advocate II on ‎04-22-2025 10:55 AM
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
Status: Completed

Hi @higgy7 ,

 

If you're talking about SQL anayalytics endpoint, you should be able to bulk delete a query by holding SHIFT + multi-select the queries you want to delete. This feature will be available in SQL database soon as well.

 

Thanks,

Yo-Lei

See more ideas labeled with:
7 Comments (7 New)
bob_duffy

maintain DatabaseID, Database Name and SqlEndPoint on a restore

Submitted on ‎01-23-2025 05:35 AM Submitted by on ‎01-23-2025 05:35 AM
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
Status: Under Review
See more ideas labeled with:
9 Comments (9 New)
Vojtech_Dolejsi

Allow calls of Fabric SQL Database stored procedures from Data Warehouse

Submitted on ‎11-21-2024 01:43 AM Submitted by on ‎11-21-2024 01:43 AM
It would be great if there were a possibility to call a SQL Database stored procedures directly from a Data Warehouse stored procedures. A use case for this would be e.g. logging activities and events during ETL loads. ... View more
Status: Under Review
See more ideas labeled with:
1 Comment (1 New)
BobDuffyIRL

Keep Database Name as Non GUID

Submitted on ‎03-19-2025 02:47 AM Submitted by on ‎03-19-2025 02:47 AM
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
Status: Planned

We will remove the guid, but I don't forsee any plans for connecting to master.

See more ideas labeled with:
  • Databases | SQL Database
4 Comments (4 New)
jboarman

Enable Connection from Fabric Notebook to Fabric SQL Database

Submitted on ‎02-01-2025 11:12 AM Submitted by on ‎02-01-2025 11:12 AM
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
Status: Planned

@jboarman - Our team is working to get Notebook integration with SQL database in Fabric. Our phase I of this feature is out - it's called magic T SQL. Now just add the below line in a cell and connect to your database easily-

%%tsql -artifact sqldb1 -type SQLDatabase -bind df2

 

please check out this document for further details - Run T-SQL code in Fabric Python notebooks - Microsoft Fabric | Microsoft Learn

 

Thanks

Sukhwant

See more ideas labeled with:
3 Comments (3 New)
rob_carrol1

Read Data from Lakehouse inside a Fabric SQL Database (using T-SQL)

Submitted on ‎01-10-2025 07:04 AM Submitted by on ‎01-10-2025 07:04 AM
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
Status: Planned
See more ideas labeled with:
2 Comments (2 New)

How to deal with garbled characters in Microsoft Fabric SQL Database

Submitted on ‎12-08-2024 09:46 PM Submitted by Anonymous on ‎12-08-2024 09:46 PM
Currently, the collation sequence for Microsoft Fabric SQL Database is set to SQL_Latin1_General_CP1_CI_AS, which means that creating tables or column names in Japanese or other languages ​​will result in garbled characters. We have also confirmed that it is currently not possible to change the collation sequence in Microsoft Fabric SQL Database. On the other hand, the collation sequence for Microsoft Fabric warehouses is set to Latin1_General_100_BIN2_UTF8, which we have confirmed will not result in garbled characters. Therefore, we believe that if we could change the collation sequence for Microsoft Fabric SQL Database, it would be possible to set it to Latin1_General_100_BIN2_UTF8, which would help prevent garbled characters. ... View more
Status: Planned
See more ideas labeled with:
3 Comments (3 New)

Connect Fabric SQL Database using Pyspark and get the result as dataframe

Submitted on ‎07-22-2025 09:48 PM Submitted by Anonymous on ‎07-22-2025 09:48 PM
Please provide a ability to semealessly connect Fabric SQL Database using Pyspark and get the result as dataframe. It should be of similar syntax such as spark.read.....   This will open lot of options. Thank you. ... View more
Status: Completed

Spark connector for SQL databases - Microsoft Fabric | Microsoft Learn

See more ideas labeled with:
2 Comments (2 New)
rob_carrol1

Read Data from Lakehouse inside a Fabric SQL Database (using T-SQL)

Submitted on ‎01-13-2025 04:32 AM Submitted by on ‎01-13-2025 04:32 AM
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
Status: Planned
See more ideas labeled with:
2 Comments (2 New)
mark_lobbezoo

Cross-database queries for live databases

Submitted on ‎12-07-2024 10:51 AM Submitted by on ‎12-07-2024 10:51 AM
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
Status: Under Review
See more ideas labeled with:
1 Comment (1 New)
filip_olason

Add guardrails to SQL DB

Submitted on ‎12-18-2024 08:37 AM Submitted by on ‎12-18-2024 08:37 AM
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
Status: Under Review

We are aware of this limitation and the challenges it causes.  

See more ideas labeled with:
2 Comments (2 New)
BillBreitenbach

Allow multiple database to be seen under the same server

Submitted on ‎12-09-2024 12:30 PM Submitted by on ‎12-09-2024 12:30 PM
Currently, databases are randomly assigned to a pool of logical servers and there is not a way to group databases under same logical server name. Please allow us to see all the SQL databases listed under the same logical server name. It would be ideal to create one connection to the server name. This eventually would make cross-database querying on the same server possible as well . ... View more
Status: Declined
See more ideas labeled with:
2 Comments (2 New)
garddolau

Fabric SQL Database - Available via Data Pipeline Stored Procedure Activity

Submitted on ‎02-27-2025 04:22 AM Submitted by Advocate III on ‎02-27-2025 04:22 AM
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
Status: Completed

@garddolau - Stored Procedure activity in pipelines does let you choose SQL database in Fabric as a source now. Please try this functionality and let us know your feedback.

Thanks

Sukhwant

See more ideas labeled with:
3 Comments (3 New)
esatterfield

Add Selective Deployment for Fabric SQL DBs in Deployment Pipelines

Submitted on ‎12-09-2024 01:36 PM Submitted by on ‎12-09-2024 01:36 PM
The transactional nature of Fabric SQL DBs means these are a great SaaS offering for application data. However, the lack of an option to support selective deployment in pipelines (e.g., deploy Table A and Table B but not Table C since it is a work-in-progress) means your solution deployments have to be all or nothing. This would also benefit Fabric DWs as well, but I'll take what I can get. 🙂 ... View more
Status: Under Review
See more ideas labeled with:
1 Comment (1 New)
data_fab_weaver

Enable scalar functions in ctes and other sql objects

Submitted on ‎08-27-2025 04:33 AM Submitted by on ‎08-27-2025 04:33 AM
I recently came across that scalar functions are now available in sql end points for warehouses and lakehouses however you are unable to call them within CTEs and other sql objects , please make this feature available  ... View more
Status: Need Clarification

Can you please clarify if this is something you want from DW or from the SQL Server capability? It should be available in SQL Server as it is supported in other versions of SQL. 

See more ideas labeled with:
2 Comments (2 New)
pmscorca

Fabric SQL database has to support fully Power BI

Submitted on ‎06-02-2025 11:49 PM Submitted by Post Prodigy on ‎06-02-2025 11:49 PM
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
Status: Completed

Hi @pmscorca , 

 

SQL database in Fabric is currently in public preview on the Fabric platform.  It is fully integrated with the Fabric platform - from OLTP SQL engine to the analytics endpoint to the lakehouse.  

 

Here is the documentation for our product: 

SQL database Overview (Preview) - Microsoft Fabric | Microsoft Learn

 

And some additional information about creating reports: 

Create reports on your SQL database in Power BI - Microsoft Fabric | Microsoft Learn

 

You can leverage direct lake query mode by connecting to the SQL analytics endpoint, which is automatically populated when you create a SQL database in Fabric.  This document contains more information:

https://learn.microsoft.com/en-us/fabric/fundamentals/direct-lake-overview 

 

--Kate

 

See more ideas labeled with:
  • Databases | SQL Database
1 Comment (1 New)
bob_duffy

Improve Fabric SQLDB Replication Support

Submitted on ‎01-23-2025 05:48 AM Submitted by on ‎01-23-2025 05:48 AM
We had a few incidents here replication either stopped completely after a data centre crash or had irrecoverable errors. In all cases we had to fully restore database or delete and start again. We need the following features to help support replication and have smoother recovery from failures Start replication on GUI and API Stop replication on GUI and by API (The existing SQLDB API works here for Fabric) Query replication state on GUI and by API Resync either one table or all tables on GUI or by API. These features would allow for recovery from issues without having to do full restores and reduce customers down time. ... View more
Status: Planned

 

@bob_duffy we do plan to enable Start & Stop replication in the next release cycle. Ability to configure select/specific custom tables is backlogged and be enabled at a later phase.

See more ideas labeled with:
2 Comments (2 New)
todd_chittenden

List SQL Endpoint on the Fabric Workspace for SQL Databases

Submitted on ‎12-18-2024 10:08 AM Submitted by on ‎12-18-2024 10:08 AM
If you add a (preview) Azure SQL Database to your Fabric Workspace, it shows under it two items: SQL Analytics Endpoint and Semantic Model. Please add the SQL Endpoint as well. And while you are at it, make the whole list able to expand and collapse with "> / v " or + / - icons. This will go a long way to user interface improvements. ... View more
Status: Need Clarification

Can you clarify this concern?  The endpoints you are listing are children of the SQL endpoint, yes?

See more ideas labeled with:
2 Comments (2 New)

Helpful resources