Comments
Sort by recent activity
Sorry for the issue you are experiencing. It may be worth raising the amount of RAM for SSMS ( as a 32-bit application it can only access a maximum of 2GB RAM - even if the system it's running on is 64-bit.) by using the Large Address Aware utility on ssms.exe (see https://www.techpowerup.com/forums/threads/large-address-aware.112556/) There are few other things may also help: 1- Try not to link large static data tables. https://documentation.red-gate.com/soc6/common-tasks/link-static-data 2- Source Control decrypts encrypted objects by default- and sometimes the decryption causes Source Control to take a long time, please make sure uncheck this option if you don't have encrypted objects.(SQL Source Control - Setup - Comparison Options - Decrypt encrypted objects) 3-Change the temp folder path so that it has enough space. 4- Try unceck the last two options: [image] / comments
Sorry for the issue you are experiencing.It may be worth raising the amount of RAM for SSMS ( as a 32-bit application it can only access a maximum of 2GB RAM - even if the system it's running on is...
Hi @Prits,
Can you confirm the full version number of your SQL Source Control and SSMS? Can you change the log level to All , reproduce the issue and attach the log file? / comments
Hi @Prits,
Can you confirm the full version number of your SQL Source Control and SSMS? Can you change the log level to All , reproduce the issue and attach the log file?
Hi @HugoKornelis
Thanks for reporting it! We have reproduced the issue in Prompt 9.0.0.3116 as well. It's logged as a bug now and please keep an eye on the release note! / comments
Hi @HugoKornelis
Thanks for reporting it! We have reproduced the issue in Prompt 9.0.0.3116 as well. It's logged as a bug now and please keep an eye on the release note!
Hi @bunyamin
Thanks for your patience with this issue.
I'm sorry to let you know that the development team hasn't been able to prioritise this work. Although we aim to fix all bugs, but 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-6713 in our internal bug tracking system and we'll reassess it again in the future.
Sorry for the inconvenience caused. / comments
Hi @bunyamin
Thanks for your patience with this issue.
I'm sorry to let you know that the development team hasn't been able to prioritise this work. Although we aim to fix all bugs, but given the s...
Hi @torsten.strauss
I'm pleased to let you know we've fixed this issue in the latest release.
Thank you. / comments
Hi @torsten.strauss
I'm pleased to let you know we've fixed this issue in the latest release.
Thank you.
Thanks for reporting!
We've logged it as a bug and please keep an eye on the release note! / comments
Thanks for reporting!
We've logged it as a bug and please keep an eye on the release note!
Hi @torsten.strauss
Thanks again for sharing this with us.
I've added a note to the bug report! / comments
Hi @torsten.strauss
Thanks again for sharing this with us.
I've added a note to the bug report!
Hi @kmccann
We are not aware of this issue. Can you please kindly upgrade to the latest version and test again? / comments
Hi @kmccann
We are not aware of this issue. Can you please kindly upgrade to the latest version and test again?
Hi @valthordruzin ,
Thanks for your patience and I'm pleased to let you know this bug is fixed in version 6.0.7. Please upgrade and let us know if you have more questions! / comments
Hi @valthordruzin ,
Thanks for your patience and I'm pleased to let you know this bug is fixed in version 6.0.7. Please upgrade and let us know if you have more questions!
Hi @valthordruzin
Thanks for reporting it! It happens when compare live database to script folder. We've logged a bug for it and please keep an eye on the release note! / comments
Hi @valthordruzin
Thanks for reporting it! It happens when compare live database to script folder. We've logged a bug for it and please keep an eye on the release note!