Comments
Sort by recent activity
Hi Torsten,
Thanks for letting us know.
We've managed to replicate the issue here and I've created an internal bug (reference: SP-6447) to track it.
Best regards,
Frederico / comments
Hi Torsten,
Thanks for letting us know.
We've managed to replicate the issue here and I've created an internal bug (reference: SP-6447) to track it.
Best regards,
Frederico
Hi John,
If you installed SSMS 2017 after installing SQL Prompt on SSMS 2014 then you will need to rerun the installer (latest version 8.0.5.1758) so that it can install into SSMS 2017 too.
However, if SQL Prompt is already installed to a version of SSMS and you update to a newer build of that same SSMS version, then SQL Prompt doesn't require a reinstall (A repair/reinstall is only needed if you install a completely new version of SSMS).
Kind regards,
Frederico / comments
Hi John,
If you installed SSMS 2017 after installing SQL Prompt on SSMS 2014 then you will need to rerun the installer (latest version 8.0.5.1758) so that it can install into SSMS 2017 too.
However...
Hi @naumad,
Thank you for reporting this.
We've been unable to replicate this using SQL Prompt 8.0.5.1758.
Can you please provide the full Select statement (or a longer SQL snippet) where the issue occurs?
Best regards,
Frederico / comments
Hi @naumad,
Thank you for reporting this.
We've been unable to replicate this using SQL Prompt 8.0.5.1758.
Can you please provide the full Select statement (or a longer SQL snippet) where the issue...
Thanks @naumad.
We can now recreate the problem locally and I have created a bug (reference: SP-6448) to further investigate.
We will let you know as soon as we have more information.
Best regards,
Frederico / comments
Thanks @naumad.
We can now recreate the problem locally and I have created a bug (reference: SP-6448) to further investigate.
We will let you know as soon as we have more information.
Best regards,...
Hi Rick,
Thank you for reporting this.
We've tried unsuccessfully to recreate the issue locally with the latest version of SQL Prompt (8.0.5.1758).
What version of SQL Prompt and SSMS/Visual Studio are you running?
Also, does anything change if you try to refresh the suggestions (Ctrl+Shift+D)?
Best regards,
Frederico / comments
Hi Rick,
Thank you for reporting this.
We've tried unsuccessfully to recreate the issue locally with the latest version of SQL Prompt (8.0.5.1758).
What version of SQL Prompt and SSMS/Visual Studio...
Hello dmans1,
We've fixed this issue in our latest version of SQL Prompt 8.0.6.1890 (installer here).
You can find more information about this release in this forum post.
Kind regards,
Frederico / comments
Hello dmans1,
We've fixed this issue in our latest version of SQL Prompt 8.0.6.1890 (installer here).
You can find more information about this release in this forum post.
Kind regards,
Frederico
Hi Torsten,
Thank you for reporting this.
I've managed to reproduce the problem locally and I've created a bug (reference: SP-6432) to track it.
Best regards,
Frederico / comments
Hi Torsten,
Thank you for reporting this.
I've managed to reproduce the problem locally and I've created a bug (reference: SP-6432) to track it.
Best regards,
Frederico
Hi @sheldonhull,
This has not yet been fixed.
If you have Options > Styles > Apply column alias style > Alias Style: alias = column, then it will apply the refactoring regardless of the affected T-SQL clause (i.e. including UPDATE).
In other words valid SQL: update #temptest
set test_column = 1
output Inserted.test_column AS test_column_new
Gets transformed to invalid SQL: update #temptest
set #temptest.test_column = 1
output test_column_new = Inserted.test_column
I've created an internal bug ticket (reference=SP-6454) to get this fixed.
Kind regards,
Frederico / comments
Hi @sheldonhull,
This has not yet been fixed.
If you have Options > Styles > Apply column alias style > Alias Style: alias = column, then it will apply the refactoring regardless of the affected T-...
Hi @misaksen,
Thanks for reporting this. We've managed to replicate the behaviour and created a Jira ticket (SP-6357).
We'll let you know as soon as we have more information.
However, there is a workaround you could try at the moment. If you change the order of the PERIOD FOR SYSTEM_TIME so it's not the first item after the ADD, formatting should work as expected: ALTER TABLE dbo.TemporalTable
ADD SysStartDate DATETIME2 GENERATED ALWAYS AS ROW START HIDDEN NOT NULL DEFAULT SYSUTCDATETIME()
, SysEndDate DATETIME2 GENERATED ALWAYS AS ROW END HIDDEN NOT NULL DEFAULT CONVERT(DATETIME2, '9999-12-31 23:59:59.99999999')
, PERIOD FOR SYSTEM_TIME (SysStartDate, SysEndDate)
Best regards,
Frederico / comments
Hi @misaksen,
Thanks for reporting this. We've managed to replicate the behaviour and created a Jira ticket (SP-6357).
We'll let you know as soon as we have more information.
However, there is a wo...
Hi @torsten.strauss
Thanks for reporting this. We've managed to reproduce it locally and we've logged it in Jira (SP-6355).
We don't yet have a timeline for investigating this, but we'll let you know as soon as we do.
Best regards,
Frederico / comments
Hi @torsten.strauss
Thanks for reporting this. We've managed to reproduce it locally and we've logged it in Jira (SP-6355).
We don't yet have a timeline for investigating this, but we'll let you kn...