Getting error while formatting SQL code.

jay2807

I'm trying to format/ refactor the stored procedure in SSMS. Stored procedure complies correctly. However, I'm getting below error while formatting it using SQL Prompt.



Error code is like below:

<div>INSERT INTO #Address</div><div>	EXEC dbo.usp_COMN_ImportAddress @Address WITH RECOMPILE;</div>

jay2807

Any update here?

Dan_J

Hi @jay2807

My sincere apology for the delay in responding to you on this.

It would be good to see a copy of your stored procedure if possible. We have raised a support ticket for this issue and I will contact you through that going forward.

jay2807

Hi, @Dan_J

I have attached stored procedure in the question.

jay2807

Hello, @Dan_J, Any update?

Dan_J

Hi @jay2807

My sincerest apology, I hadn't spotted your updates on this before now! Thanks very much for confirming that you have provided your stored procedure.

I have been able to replicate the issue you are seeing, and I will very shortly be discussing this with my colleagues. In the mean time, please can you confirm which version of SQL Prompt you are currently using?

Dan_J

Hi @jay2807

Just to update you on this, our development team have taken this on and will be working on it. I will update you again on this as soon as I hear anything from them.

jay2807

@Dan_J, I'm using SQL Prompt Version 10.6.5.18584

Dan_J

Hi @jay2807

Our development team have taken a look at this. It appears there is a bug in the Microsoft parser, and so they have logged this with Microsoft. Unfortunately we are at the mercy of if/when Microsoft chose to fix this.

Again, I will update you on this as soon as I have more information.

jay2807

Hi @Dan_J, Any updates?

jay2807

Hello, @Dan_J, Any update?

Dan_J

Hi @jay2807!

I am so sorry for the delayed reply to you on this! There appears to have been some confusion at this end, around working on a fix for this issue/bug.

Given the nature of this bug, unfortunately we are essentially unable to work on a fix for this ourselves until  Microsoft have released a fix also. While we can't say when they are likely to work on this, we don't see it being within the next 6-12 months.

We do appreciate that this is not ideal for you, or anyone else who may be experiencing this issue, and so we will continue to press Microsoft for a solution to this. We have also logged a ticket for this and will keep it on hold for our visibility.

jay2807

@Dan_J, Can you post the ticket link here in the comment that you logged to Microsoft, please?

Dan_J

Hi @jay2807

Sure, the link to the ticket is: https://github.com/microsoft/sqltoolsservice/issues/1181