Keep Database Name as Non GUID

[BobDuffyIRL]

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

[akatesmith]

If we plan to remove the GUID from the database name, will this satisfy your needs?

[BobDuffyIRL]

This will help a bit., ut it still stands that Fabric SQLDB is one of the only SQL editions that we must enter a database name when connecting with SSMS. Other editions allow connection just to master then a change in DB after connection. If the default DB was set to the SQLDB then SSMS would work much more smoothly. I added another idea for this. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Make-the-user-database-the-default-instead-of... This makes sense as we can only have one SQLDB per Fabric database connection end point. So if we can only have one, why not make it the default!

[BobDuffyIRL]

This will help a bit, but it still stands that Fabric SQLDB is one of the only SQL editions that we must enter a database name when connecting with SSMS. Other editions allow connection just to master then a change in DB after connection. If the default DB was set to the SQLDB then SSMS would work much more smoothly. I added another idea for this. https://community.fabric.microsoft.com/t5/Fabric-Ideas/Make-the-user-database-the-default-instead-of... This makes sense as we can only have one SQLDB per Fabric database connection end point. So if we can only have one, why not make it the default!

[akatesmith]

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