Comments
5 comments
-
Just for information, we have to manipulate at lot of big SQL files (size of +/- 15mb)
-
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.
-
Hi,
It seems that, until now, no more crash on SSMS 17.4 ...
Thanks
Confluence -
Hi @sklinck
Thanks for your reply.
That's good to hear. Please keep us posted! -
Thank you! This really helped.
Add comment
Please sign in to leave a comment.
We have already tested the SQL Prompt few years ago (version 7) but we stopped to use it because of frequently error message as
- System.OutOfMemoryException in the result page
- Insufficient memory to continue the execution of the program (mscorlib) , modal window
- The system cannot find the file specified when opening a document.
All these errors disappears when I disable the addin ... and return after some minutes after re-enabling the addin.
I just download the latest trial version of SQL Prompt Pro but the problems are always there ...
Do you have an idea ?
For information : Win7SP1 + 8Go Ram + recent I5 + SSD 256Go + SQL Management Studio 2014 SP2 (tools)
Thanks