Fabric Ideas

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

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 we restore a Fabric SQLDB it changes the database names which break the ETL and all customers connecting to it.  We then have to ge everyone globally to change the connection string, which means a restore has customer downtime of days.   Can you fix this so that a restore keeps the original database name and doesnt break the connection string ?   Ideally a restore shoudl restore "as was" unless we choose to restore to a different Artefact Name or workspace.     ... 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

Currently when using SQLDB if we enter the server name / dns into SSMS or another tool it will fail as the connection defaults to master and the yser has no rights. We then have to manually add database, which is a GUID iso impossible to remember!   Please allow the user(s) public rightsr in the master so that we can connect in SSMS and other tools and then select the database from pull down.   This is how every other edition of SQL works! ... View more

Hi Team, Great to get the ability to create a SQL Database via API are you working on the ability to return the connection details? To make it more useful it would be great if we could get the connection details for the created database to (similar to how we can get in warehouse).   ** Once completed can we update the offical documentation ASAP so the Terraform provided team can start using **   Return something like below:   {   "id": "5b218778-e7a5-4d73-8187-f10824047715",   "displayName": "SQLDatabase1",   "description": "A SQLDatabase description.",   "type": "SQLDatabase",   "workspaceId": "cfafbeb1-8037-4d0c-896e-a46fb27ff229"   "properties": {     "serverFqdn": "dqjx2zrgh4uejnetrut54cdkau-g3353rbpoubuvclqhgoznhkmji.database.fabric.microsoft.com",     "databaseName": "SQLDatabase1-b218778-e7a5-4d73-8187-f10824047715"   }, }   Thanks, Darren ... 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 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

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

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

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

It would really help with backwards compat and frustrations connecting in SSMS if Fabric SQLDB allowed users to connect to master. This adds 2 improvements 1) In this way we could connect to SSMS and then change DB afterwards , which is very much a mainstream practice. we understand telemetry shows that this is the No1 connection error from SSMS. 2) Currently some features such as dacpac, VS package export from SSMS and 3rd party schema compares break due to this issue. ... 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

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

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

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

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

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

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