SQL Complete - SQL 2005 - Frequently crashes.

[alexa]

Thank you for updating us on this issue. Please let us know if the issue happens with the new version 4.0.53 of dbForge SQL Complete.

[rprince]

kamiller, you may be able to use version 3.1.21

Been having the same issue since version 3.5 came out. I have attempted to use all the versions since the release of 3.5 including the latest version 4. I have the same issues you mention. After about the 3rd crash in one day I usually just reinstall version 3.1.21. I can run this version with only an occasional crash every now and then (like once a month).

Worked with support for a 2 month period (case #36664) and we never had any luck identifying the issue. My specs are similar to the ones mentioned.

[alexa]

Hello kamiller42,

Could you please update us on the status of the issue?

[kamiller42]

I downloaded the latest version and performed an update. 30 minutes later, SSMS crashed. So,I uninstalled, including settings, and installed the latest. System crashed 2 hours later.

It is still crashing and the same way... when it pops up the context options window.

[alexa]

Could you please try to download and install Microsoft .NET Framework 3.5 Service Pack 1:
http://www.microsoft.com/en-us/download ... aspx?id=22

Please also try using Microsoft SQL Server 2008 R2 Management Studio Express:
http://www.microsoft.com/en-us/download ... x?id=22985

Please let us know the result.

[kamiller42]

I did a repair install of .NET 3.5 SP1. Getting SSMS 2008 was a challenge, partly because MS installers vary in approach and slow. I had to maintain SSRS 2005 while having SSMS 2008. After taking a very long installation path, I ended up with SSMS 2008 while maintaining SSRS 2005.

So far, SQL Complete is a solid product when paired with SSMS 2008. It's so much better that I think removing SQL 2005 for SQL Complete's list of compatible environments should be seriously considered.

[alexa]

Please try to install the latest build of Management Studio 2005 available on Microsoft's website as we do not guarantee correct functioning of dbForge SQL Complete with earlier builds of Management Studio 2005 since they are not available for downloading anymore on the official Microsoft's website, so we can not run tests for compatibility of dbForge SQL Complete with the earlier builds of Management Studio 2005.

[kamiller42]

I listed the software versions I have in prior post. I had the latest SSMS 2005, 9.00.4035.00. Do you know a newer version? Appreciate a link.

SSMS 2008 will work for me, mainly because it doesn't crash. I do need to figure out how to get the Profiler back. Saw a blog post say it was possible to get Profiler with Express. If not, I will probably have to go back to 2005.

[alexa]

Finally, we were able to reproduce this issue and will fix it in the next build of dbForge SQL Complete. The problem lies in GDI objects leaking in the SSMS 2005 code that is called from dbForge SQL Complete.

[alexa]

We would like to let you know that the new build 4.0.65 of dbForge SQL Complete, where the issue you reported is fixed, has been released and is available for downloading: http://www.devart.com/dbforge/sql/sqlco ... nload.html

Thank you for your help in improving dbForge SQL Complete.

Also, Devart is happy to tell you that we released dbForge Studio Beta for MySQL 6.0: http://www.devart.com/news/2013/dbforge ... 0beta.html

You can try out dbForge Studio for MySQL, beta v6 here: http://www.devart.com/dbforge/mysql/stu ... nload.html

We are looking forward to your feedbacks!