Settings and activity
16 results found
-
24 votes
Craig Anderson supported this idea ·
-
24 votes
Craig Anderson supported this idea ·
-
29 votes
Craig Anderson supported this idea ·
-
31 votes
Craig Anderson supported this idea ·
-
32 votes
Craig Anderson supported this idea ·
-
33 votes
Craig Anderson supported this idea ·
-
35 votes
Craig Anderson supported this idea ·
-
38 votes
Craig Anderson supported this idea ·
-
54 votes
Craig Anderson supported this idea ·
-
74 votes
Craig Anderson supported this idea ·
-
3 votes
Craig Anderson supported this idea ·
-
6 votes
Craig Anderson supported this idea ·
-
6 votes
Craig Anderson supported this idea ·
-
5 votes
Craig Anderson supported this idea ·
-
35 votes
An error occurred while saving the comment Craig Anderson supported this idea ·
An error occurred while saving the comment Craig Anderson commented
Working with MS-Fabric Lakehouses and Warehouses is becoming as important as working with our regular MS SQL Servers.
Right now, my team is getting around this by using SSMS 21 (preview) without SQL Prompt installed for Fabric work and regular SSMS 20 for work with our on-prem and Azure SQL server instances.
This is not a great long-term solution. We're starting to get used to not having SQL Prompt in the Fabric environment....
-
6 votes
Craig Anderson shared this idea ·
Even if you don't add support for Fabric warehouses and lake houses soon, please detect that the current connection is to a Fabric object and quietly disable SQL Prompt's IntelliSense so it stops crashing when I connect to a Fabric lake house or warehouse.
Keeping the formatting working would still be nice though.