Fabric Ideas

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

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

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

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

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

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

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

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

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

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

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

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

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

Hi ”Product team” Currently customers with private link enables on Fabric teanant at the start of the preview on November 19 cannot create a Fabric SQL database. Any change that this will change? I am making a POC on moving our workflow from Synapse to Fabric and thought that the Fabric SQL data base might be a good choice for custom logging (our data go to a lakehouse) but a bit surprised to find we are not able to even create a Fabric SQL database as we must use private link due to company policy.   Friendly regards Kim Tutein ... View more

Prezados, Gostaria de propor a inclusão de uma funcionalidade no Power BI relacionada à unidade de medida "quilogramas" (kg). Atualmente, encontramos certa dificuldade em configurar os gráficos de modo que os dados sejam exibidos diretamente em kg, sem a necessidade de criar medidas ou fórmulas específicas. Essa mudança seria muito útil, considerando que diversas bases de dados já utilizam essa unidade de medida como padrão. A inclusão de uma configuração nativa para quilogramas economizaria tempo e tornaria os processos de visualização mais eficientes, especialmente para equipes que lidam com grandes volumes de dados relacionados a peso. Acredito que essa melhoria pode beneficiar não apenas nossa equipe, mas também outros usuários que enfrentam desafios semelhantes ao trabalhar com gráficos que envolvem unidades de massa. ... View more

Currenlty when connecting to a Database using SSMS we get an error if we dont put the name of the database in the COnneciton Properties (and no one ever remembers to do this). This leads for poor user experience and goes against "it just works" If the user had automatic rights in master (even just connect, then there would be no error message. ... View more

When trying to browse list of databases to select correct one in SSMS or SSDT, we get error message below TITLE: Browse Server for Database ------------------------------ Database 'master' on server 'fkm4vwf6l6zebg4lqrhbtdcmsq-absyvg6llsuutcc3wwyid37nou.database.fabric.microsoft.com' is not currently available. Please retry the connection later. If the problem persists, contact customer support, and provide them the session tracing ID of '{6745DA45-6CB6-46FB-9E2A-DD54D201E9F7}'. (Microsoft SQL Server, Error: 40613) For help, click: https://docs.microsoft.com/sql/relational-databases/errors-events/mssqlserver-40613-database-engine-error ------------------------------ BUTTONS: OK ------------------------------ ... View more

SQL analytics endpoints for Data Warehouses support time travel using syntax such as "FOR TIMESTAMP AS OF". It would be great if this would also be added to SQL analytics endpoints Data Lakehouses.   Other ways to access the changes or delta table versions from the SQL analytics endpoints would be welcome too.   Thanks! ... View more