Comments
Sort by recent activity
Hi @higgim Thanks for your patience with this issue. Unfortunately the development team hasn't been able to prioritise this work. Given the size of the backlog of higher-priority items, it doesn't look like it's something we will fix in the foreseeable future. However we still have it logged as SP-6242 in our internal bug tracking system and we'll reassess it again in the future. Please keep an eye on the release note! / comments
Hi @higgim Thanks for your patience with this issue.Unfortunately the development team hasn't been able to prioritise this work. Given the size of the backlog of higher-priority items, it doesn't l...
Hi @MGH_Admin Can you please try:
Disable the built-in intellisense under Options->Text Editor->Transact-SQL->Intellisense (this has been known to clash with Prompt in the past and cause slowdowns due to excessive memory usage)
Go to SQL Prompt>Options, click on Export to save your settings, and then try a "Restore all defaults" to see if that makes any difference? (You can then import the original settings back.)
Disable the auto-refresh experimental feature (SQL Prompt ->Options->Labs-> Experimental features) (it might be kicking in at the wrong time and causing the slow down)
/ comments
Hi @MGH_Admin Can you please try:
Disable the built-in intellisense under Options->Text Editor->Transact-SQL->Intellisense (this has been known to clash with Prompt in the past and cause slowdowns ...
Hi @DBAJohnny and @mbray ,
Thanks for your patience with this issue.
Our development team has done some work relating to this issue in the latest release.
Can you please upgrade or use this installer and let us know if it helps? / comments
Hi @DBAJohnny and @mbray ,
Thanks for your patience with this issue.
Our development team has done some work relating to this issue in the latest release.
Can you please upgrade or use this instal...
Hi @DBAJohnny, Thanks for the update and do let us know if issue reoccurs! / comments
Hi @DBAJohnny, Thanks for the update and do let us know if issue reoccurs!
Hi @mbray , Thanks for posting and I'll update the bug report with your comments! Thanks! / comments
Hi @mbray , Thanks for posting and I'll update the bug report with your comments! Thanks!
Hi @DBAJohnny
Thanks for the update.
Please go to SQL Prompt- Help -Enable verbose logging.
Thanks. / comments
Hi @DBAJohnny
Thanks for the update.
Please go to SQL Prompt- Help -Enable verbose logging.
Thanks.
Hi @DBAJohnny
Thanks for your reply.
We appreciate your concern of publishing your scripts here. We'll be in touch through email shortly.
Thanks. / comments
Hi @DBAJohnny
Thanks for your reply.
We appreciate your concern of publishing your scripts here. We'll be in touch through email shortly.
Thanks.
Hi @DBAJohnny
Thanks for your update and we've logged this issue as SP-6767 in our internal bug tracking system.
It would be very helpful if you can enable verbose logging, reproduce the sluggishness (with Code Analysis on apparently) and send in the log file.
Thanks! / comments
Hi @DBAJohnny
Thanks for your update and we've logged this issue as SP-6767 in our internal bug tracking system.
It would be very helpful if you can enable verbose logging, reproduce the sluggishn...
Hi @DBAJohnny
Thanks for posting.
Our development team has lined up some work to improve Prompt in term of slowness issue. It would be very helpful if you could:
1- Confirm how many tabs do you have open when the issue started
2- Confirm if disable Code Analysis function make any difference
3- Share a sample script with us in order to reproduce the issue locally here
4- Confirm the full version number of your SQL Prompt
Thanks for your assistance and sorry for the inconvenience caused. / comments
Hi @DBAJohnny
Thanks for posting.
Our development team has lined up some work to improve Prompt in term of slowness issue. It would be very helpful if you could:
1- Confirm how many tabs do you hav...
Hi @sklinck
Thanks for posting and sorry to hear you are having these issues.
Could you please try the suggestions mentioned here?
SSMS is a 32-bit application and as a result it can only access a maximum of 2GB RAM - even if the system it's running on is 64-bit.
By making SSMS large address aware, it will allow SSMS to use more RAM and that should help. To do this, please:
1- Close SSMS
2- Download the large address aware tool from here: https://www.techpowerup.com/forums/attachments/laa_2_0_4-zip.34392/
3- When you launch the tool, select ssms.exe as the executable - it will usually be located in a path like this - C:\Program Files (x86)\Microsoft SQL Server\xxx\Tools\Binn\ManagementStudio\ssms.exe (where xxx is your ssms version number)
4- Tick the "Check this box to enable the application to use more than 2GB of memory" checkbox
5- Click Save
I hope this helps.
Regarding the third issue, would you be able to share a screenshot of the error?
Thanks. / comments
Hi @sklinck
Thanks for posting and sorry to hear you are having these issues.
Could you please try the suggestions mentioned here?
SSMS is a 32-bit application and as a result it can only access a ...