Comments
Sort by recent activity
It's now July. I'm using SSMS 20.1. I can no long downgrade my SQL Prompt to regain the main reason I pay for the add-in and the subject of much of its marketing – so I'm left wondering if I should just save my money as I'm "coping" with having to type table & column names. I mean, the ability to format the SQL to my liking is all very fine, but that's a nice addition to core functionality, core functionality that's now been missing for some time. / comments
It's now July. I'm using SSMS 20.1. I can no long downgrade my SQL Prompt to regain the main reason I pay for the add-in and the subject of much of its marketing – so I'm left wondering if I should...
2024-04-18 13:52:14.864 -05:00 [Warning] Failed to load server xxxxxxxx Microsoft.Data.SqlClient.SqlException (0x80131904): Login failed for user '<token-identified principal>'. at Microsoft.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) at Microsoft.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) SSMS 19.3.4 SQLPrompt 10.14.14.8187 Authentication is using Microsoft Entra MFA to managed instances in Azure. I've been without a functioning SQL Prompt for a while now. Recently re-upped the license, but am beginning to ask "If I can 'manage' without it, why pay?" A question that's becoming harder to answer, as you might imagine, as the days without a fix go by.[image]
/ comments
2024-04-18 13:52:14.864 -05:00 [Warning] Failed to load server xxxxxxxxMicrosoft.Data.SqlClient.SqlException (0x80131904): Login failed for user '<token-identified principal>'. at Microsoft.Data....