Comments
7 comments
-
Hello,
Same issue after updating SQL Prompt this morning.
Current SQL prompt version is : 9.1.4.4532.
Maxime
-
Hi guys,
Thanks for the post!
As mentioned over my email to both of you, we are investigating the issue and would like to get further details from you.
-
I am having the same problem as above.
SSMS: 17.6
SQL Prompt: 9.1.4.4532
SQL Server 2014 - SP2
Sample Code which errors when attempting to format:USE [master];<br>GO<br><br>DECLARE @p1 BIGINT;<br>SET @p1 = 123456789012345;<br>GO<br><br>--DROP TYPE [dbo].Junk;<br>CREATE TYPE [dbo].[Junk] AS TABLE<br> ([JunkID] UNIQUEIDENTIFIER NOT NULL,<br> [Name] VARCHAR(25) NOT NULL,<br> [Value] VARCHAR(100) NULL,<br> [GUID] UNIQUEIDENTIFIER NOT NULL,<br> [TimeStampUTC] DATETIME NOT NULL);<br>GO<br><br>DECLARE @p0 dbo.Junk<br>GO
Thanks,
Tony Green
-
Same here!
The formatting fails for ALL scripts but if I copy the statement to a new fresh query window it will work for me.
I played around with different code page settings when saving the.sql file but this did not help neither.
I am just wondering why it tells that this error is related to unicodestrings ....
Torsten
-
Hi @torsten.strauss @TonyGreen @MaximeBOTOKAPOAKA
Sorry for the issue you are having.
We have it logged as SP-6888 in our internal bug tracking system.
Can you please uncheck "Prefix N to unicode literal string variable assignments"? It should resolve the issue.
-
Hello,
issue solved by uncheck of "Prefix N to unicode literal string variable assignments".
Thks, have a nice day. -
Hi @torsten.strauss @TonyGreen @MaximeBOTOKAPOAKA
Thanks for your patience with this issue.
I'm pleased to let you know the bug is fixed. Please upgrade to the latest version.
Thanks.
Add comment
Please sign in to leave a comment.
After upgrading to the latest version I got the mentioned error for every! SQL code line I would like to format.
I consider this as a critical bug cause I cannot use SQL Prompt anymore.
Would be nice if you find a solution for this issue.
Thanks!
Torsten