Comments
Sort by recent activity
ostandage said:
Hi @VisualDragon We had to make some changes to support MFA authentication in SSMS 19 Preview 3, which unfortunately has means we no longer support MFA connections in Preview 2. If you upgrade to Preview 3 (release in August), you should be able to continue using MFA connections. @ostandage After installing 10.12.6.30951 it started working again in Preview 2. I will definitely update to Preview 3 though. Thanks!
/ comments
ostandage said:
Hi @VisualDragon We had to make some changes to support MFA authentication in SSMS 19 Preview 3, which unfortunately has means we no longer support MFA connections in Preview ...
Using SSMS v19 Preview 2. Connected to an Azure SQL Server (not a managed instance, the virtual server behind an Azure SQL Database) using Azure Active Directory - Universal with MFA. Right-click on a database and select New Query. I am presented with the SQL Prompt Crash Dialog and am now caught in a crash loop. Submitting the error report or hitting Cancel takes me right back into the crash dialog. I have to End Task SSMS in Task Manager. This just started after updating to the latest version 10.12.5.30313. Anyone else experience this? / comments
Using SSMS v19 Preview 2. Connected to an Azure SQL Server (not a managed instance, the virtual server behind an Azure SQL Database) using Azure Active Directory - Universal with MFA. Right-click...
+1 for Intellisense and AutoComplete. / comments
+1 for Intellisense and AutoComplete.
Would have been nice if this incompatibility was called out in the Known Issues for SSMS 18.5 https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver15#known-issues-185 I find it very disappointing that a "dot" release of SSMS breaks a tool as popular as SQL Prompt, forces an upgrade to same, and the incompatibility is not called out. / comments
Would have been nice if this incompatibility was called out in the Known Issues for SSMS 18.5https://docs.microsoft.com/en-us/sql/ssms/release-notes-ssms?view=sql-server-ver15#known-issues-185I fin...
I have SQL Prompt 9 installed and activated. I switched to a different user account on the same machine and SQL Prompt shows as activated there as well. I believe that the "Per user" part of the license pertains to your Red-Gate account. In fact, I installed it under one desktop account, activated it under the other desktop account, switched to the first desktop account, and SQL Prompt showed that is was already activated there. So, looks like multiple desktop accounts on the same machine works fine. You'll probably be prompted to login with your Red-Gate account when you first run SQL Prompt under a new account and then it should all work just fine. / comments
I have SQL Prompt 9 installed and activated. I switched to a different user account on the same machine and SQL Prompt shows as activated there as well. I believe that the "Per user" part of the ...
Cool. I have repeated what you have described and can confirm that this happens to me as well. I am running SQL2005 SP2.
[Edit]
Actually, I did not crash (at least not yet) and clicking on the close x for the query did eventually bring up the save dialog and I could just click No and all was then well. That is about all I could do though.
Dave / comments
Cool. I have repeated what you have described and can confirm that this happens to me as well. I am running SQL2005 SP2.
[Edit]
Actually, I did not crash (at least not yet) and clicking on the cl...
I can also confirm that SQL Prompt 3 works very well with Office 2007 installed. I experienced no issues at all. I was also running on Vista Ultimate and found no problems there. In fact, Version 3 is required IMHO for Vista as version 2 runs very slow and does some weird things.
You can actually watch it back up and type out the snippets as if you were typing it yourself. Neat to watch but completely unusable. / comments
I can also confirm that SQL Prompt 3 works very well with Office 2007 installed. I experienced no issues at all. I was also running on Vista Ultimate and found no problems there. In fact, Versi...
The word "refactor" comes to mind. A 3500 line script is madness.
My $0.02 / comments
The word "refactor" comes to mind. A 3500 line script is madness.
My $0.02
The only time I experienced horrible performance due to SQL Prompt was after installing a service pack. (for Visual Studio OR SQL Server) I found that uninstalling and reinstalling SQL Prompt fixed everything up. This has happened to me a couple of times. / comments
The only time I experienced horrible performance due to SQL Prompt was after installing a service pack. (for Visual Studio OR SQL Server) I found that uninstalling and reinstalling SQL Prompt fixe...
Hi Tilman,
See screen shot here: http://www.totzke.ca/sqlprompt.jpg
I cleared the cache and closed all current connections. The problem still exists. All columns that are nvarchar(50) were created as such originally and display in SQL Prompt as nvarchar(100). You will see a column now that is nvarchar(300) and SQL Prompt shows it as nvarchar(600).
It is likely that SQL Prompt is relying on the column length which for nvarchar columns shows up as double because of their support for DBCS.
Dave / comments
Hi Tilman,
See screen shot here:http://www.totzke.ca/sqlprompt.jpg
I cleared the cache and closed all current connections. The problem still exists. All columns that are nvarchar(50) were created...