Comments
Sort by recent activity
Hi @...,
Are you and your user using the same version of SQL Prompt?
Your user should try to upgrade his version. This is the link to the latest SQLPrompt release.
Kind regards,
Fabiola / comments
Hi @...,
Are you and your user using the same version of SQL Prompt?
Your user should try to upgrade his version. This is the link to the latest SQLPrompt release.
Kind regards,
Fabiola
Hi @yashar999,
We are no longer supporting SQL Server 2008 R2 version (see SQL Prompt v8 documentation).
You can upgrade your SSMS for free here.
Regards,
Fabiola / comments
Hi @yashar999,
We are no longer supporting SQL Server 2008 R2 version (see SQL Prompt v8 documentation).
You can upgrade your SSMS for free here.
Regards,
Fabiola
Hello @TheRightAmount,
This issue should be fixed in our latest version of SQL Prompt 8.2.5.2924 (installer here).
You can find more information about this release in this forum post.
Kind regards,
Fabiola / comments
Hello @TheRightAmount,
This issue should be fixed in our latest version of SQL Prompt 8.2.5.2924 (installer here).
You can find more information about this release in this forum post.
Kind regards,...
Hi @TheRightAmount,
Thank you for reporting this issue. Which SQL Prompt version are you using? Unfortunately, we are unable to reproduce it with the latest version of SQL Prompt.
We have used the Default style settings + "Align data types and constraints" checkbox checked. CREATE TABLE Persons
(
Code CHAR(6) NOT NULL,
CountryCode CHAR(3) NULL,
Name NVARCHAR(255) NULL,
AddressLine1 NVARCHAR(255) NULL,
AddressLine2 NVARCHAR(255) NULL,
AddressLine3 NVARCHAR(255) NULL,
AddressLineAddressAddressLineAddressAddressLineAddressLineAddressLine3 NVARCHAR(255) NULL,
City NVARCHAR(50) NULL,
);
Best wishes,
Fabiola / comments
Hi @TheRightAmount,
Thank you for reporting this issue. Which SQL Prompt version are you using? Unfortunately, we are unable to reproduce it with the latest version of SQL Prompt.
We have used the ...
Hi @Ashley,
This issue is resolved in the latest version of SQL Prompt, v8.0.8.2086. You can update to this from SQL Prompt>Help>Check for updates.
I hope this helps but please let me know if there are any further issues for you!
Best regards,
Fabiola / comments
Hi @Ashley,
This issue is resolved in the latest version of SQL Prompt, v8.0.8.2086. You can update to this from SQL Prompt>Help>Check for updates.
I hope this helps but please let me know if there...
Hello @sdks,
This issue should be fixed in our latest version of SQL Prompt 9.0.3.3299 (installer here).
You can find more information about this release in this forum post.
Kind regards,
Fabiola / comments
Hello @sdks,
This issue should be fixed in our latest version of SQL Prompt 9.0.3.3299 (installer here).
You can find more information about this release in this forum post.
Kind regards,
Fabiola
Hi @sdks,
Thank you for reporting this. I've managed to reproduce the problem locally and I've created a bug (reference: SP-6558) to track it.
Best regards,
Fabiola / comments
Hi @sdks,
Thank you for reporting this. I've managed to reproduce the problem locally and I've created a bug (reference: SP-6558) to track it.
Best regards,
Fabiola
Hi @naumad,
Thanks for letting us know.
In order to replicate the issue here we would need your SQLPrompt log file and also your Formatting Styles file. Could you please attach them to this discussion?
Best regards,
Fabiola / comments
Hi @naumad,
Thanks for letting us know.
In order to replicate the issue here we would need your SQLPrompt log file and also your Formatting Styles file. Could you please attach them to this discuss...
Hi @naumad,
Thank you for the files. We have created a bug (reference: SP-6560) to investigate the problem and to track it.
Best regards,
Fabiola / comments
Hi @naumad,
Thank you for the files. We have created a bug (reference: SP-6560) to investigate the problem and to track it.
Best regards,
Fabiola
Hi @ZackS,
Thank you for reporting this. We've reproduced the problem locally and created a bug (reference: SP-6559) to track it.
Best regards,
Fabiola / comments
Hi @ZackS,
Thank you for reporting this. We've reproduced the problem locally and created a bug (reference: SP-6559) to track it.
Best regards,
Fabiola