Comments
Sort by recent activity
Hi @padigan,
This is a known issue in the installer. If you right click on the top bar and select Log File..., can you send us the contents of the log?
To fix the issue you need to navigate to %localappdata% and delete the Temp directory. If you re-run after doing that it should be fixed [image]
Hope this helps!
James / comments
Hi @padigan,
This is a known issue in the installer. If you right click on the top bar and select Log File..., can you send us the contents of the log?
To fix the issue you need to navigate to %loc...
Hi @Phil,
Thanks for your post. Unfortunately SQL Prompt no longer supports SSMS 2008R2 and lower. You can upgrade your version of SSMS for free here
Hope this helps!
James / comments
Hi @Phil,
Thanks for your post. Unfortunately SQL Prompt no longer supports SSMS 2008R2 and lower. You can upgrade your version of SSMS for free here
Hope this helps!
James
Hi @Santosh_Mavuduri ,
Thanks for your post! Unfortunately when you install a new version of SSMS SQL Prompt does not automatically add itself so you will have to uninstall and reinstall SQL Prompt to get it to appear.
Hope this helps!
James / comments
Hi @Santosh_Mavuduri ,
Thanks for your post! Unfortunately when you install a new version of SSMS SQL Prompt does not automatically add itself so you will have to uninstall and reinstall SQL Prompt...
Hi again @gvarol@corelogic.com ,
Just to let you know we've just released version 8.0.3.1587 of SQL Prompt which should fix this issue.
Regards,
James / comments
Hi again @gvarol@corelogic.com ,
Just to let you know we've just released version 8.0.3.1587 of SQL Prompt which should fix this issue.
Regards,
James
Hi @gvarol@corelogic.com ,
Thanks for the post! I've managed to track this down to the CASE statement inside a select column list. If the WHEN clause has multiple conditions then the error occurs. We've logged the error here and will look into it this week.
As a workaround for now you can go to SQL Prompt > Options > Format > Styles and uncheck the 'Apply column alias style' checkbox [image]
Hope this helps!
James / comments
Hi @gvarol@corelogic.com ,
Thanks for the post! I've managed to track this down to the CASE statement inside a select column list. If the WHEN clause has multiple conditions then the error occurs. ...
Hi @jbrune,
Thanks for noticing this! We've managed to reproduce this here, we'll hopefully investigate this week.
Regards,
James / comments
Hi @jbrune,
Thanks for noticing this! We've managed to reproduce this here, we'll hopefully investigate this week.
Regards,
James
Hi bunyamin ,
Thanks for your post. We've recently released version 8.0.2 of SQL Prompt which I think fixes this issue. You can download the update from inside SSMS by going to SQL Prompt > Help > Check for Updates or by downloading it here
I hope this helps!
James / comments
Hi bunyamin ,
Thanks for your post. We've recently released version 8.0.2 of SQL Prompt which I think fixes this issue. You can download the update from inside SSMS by going to SQL Prompt > Help > ...
Hey again @torsten.strauss ,
We've just released version 8.0.3.1587 of SQL Prompt which should contain a fix for this issue [image]
Hope this helps!
James / comments
Hey again @torsten.strauss ,
We've just released version 8.0.3.1587 of SQL Prompt which should contain a fix for this issue
Hope this helps!
James
Hi @torsten.strauss ,
Thanks for reporting this, it's an issue with the backwards compatible create index syntax (seen here ). We've got a fix for it here but as a workaround you can put the FILLFACTOR token in parenthesis and that should allow you to format [image]
Hope this helps!
James / comments
Hi @torsten.strauss ,
Thanks for reporting this, it's an issue with the backwards compatible create index syntax (seen here ). We've got a fix for it here but as a workaround you can put the FILLFA...
Hi David,
Thanks for noticing this! It's definitely a bug, I've found a fix here and will hopefully have it released in the next few days. I've logged this internally as SP-6361.
Regards,
James / comments
Hi David,
Thanks for noticing this! It's definitely a bug, I've found a fix here and will hopefully have it released in the next few days. I've logged this internally as SP-6361.
Regards,
James