Comments
Sort by recent activity
I can confirm I have been seeing this as well, but with SQL Data Compare v13. At one point I had it consuming over 33 GB. [image] . It was fairly easy for me to reproduce (though in all fairness it was against a database which had four tables that had 1.8 million records)
- Run compare on large table #1 (~1.8 million records)
- Generate script
- Deploy script
- Run compare on large table #2 (~1.8 million records)
- Generate script
- Deploy script
- Memory usage will be fairly large at that point
Aside from restarting the tool, I can't provide a better answer. All that I can say is I have seen this happen as well, typically with Data Compare, but it is not uncommon with SQL Compare either. / comments
I can confirm I have been seeing this as well, but with SQL Data Compare v13. At one point I had it consuming over 33 GB. . It was fairly easy for me to reproduce (though in all fairness it was a...