Sparx Systems Forum
Enterprise Architect => Bugs and Issues => Topic started by: akede on February 19, 2008, 01:45:10 am
-
Hi all,
We have a strange issue. Using EA with MS SQL as database is on some clients extremely slow and on others as fast as using a local file. It seems there is some reason related to the database connection.
Is this a known issue?
Thanks
Alex
-
EA is very chatty with the DB. If you are connected over a slow network you will encounter a slow-down in response time.
-
Hi Thomas,
The strange thing is that I'm sitting here next to a colleague with the same network connection. His connection is fast, mine is slow.
The only visible difference is that he is running XP while I'm running Vista.
Alex
-
I wonder what that tells us. Seriously though, since I am now using Vista.
My guess is that Vista might be handling the connection differently. Beyond that it could be anything from settings, to privilege, to encryption. Check your SQL Server documentation - the most recent stuff that came with your most recent service pack - to see if there are any Vista notes that would apply.
You might also want to send a report to Sparx, they take this kind of thing seriously. It would probably help if you attach a project where this happens. You can use Project Transfer to extract the project. Also send Sparx the DSN file (or the connection string) if possible.
If you do find anything, please post back.
David
-
Not a real answer, but Vista might be the cause :-?
-
Not a real answer, but Vista might be the cause :-?
That's what really worries me. There is a lot going on under the covers with Vista. While much of it is the OS trying to 'help' us, and 'protect' us, it can really get in the way. Much of it is either undocumented, or buried someplace inaccessible (at least to me).
But it could be any number of configuration issues, one of which is tweaking Vista the wrong way.
This could be very tricky to resolve...
MySQL has always allowed broad customization, including many third-party drivers. That very flexibility has spawned an enormous number of possible configurations. Many of these have quirks, some of which show up after minor (i.e. build level) version changes.
Another version-oriented thing to check is the version of MS database drivers you have. Each Windows operating system has had a different 'native' version of MDAC included. I don't doubt that the one in Vista is also unique. Given that MDAC seems to be obsolescent, Vista might have something similar that is not available for other systems. [I'm guessing here, but it is probably worth checking out.]
HTH, David
-
I wrote a support ticket - no answer yet, but I'm sure it will come soon.
I'll keep you posted.
Alex
-
just so everyone in this thread knows..
When you say MS SQL, do you mean MySQL or SQL Server?
-
Oops,
Me too. I somehow - sadly not the first time - misread the original post.
With luck this is a repeat of earlier issues with MS SQL (as per the original) and the problem can be addressed as before. There will likely still be considerable 'chatter' but that's EA.
David
-
You got mixed up with another MySQL thread currently going on...
-
Now that we're beginners again that's bound to happen.
-
just so everyone in this thread knows..
When you say MS SQL, do you mean MySQL or SQL Server?
Microsoft SQL Server
Alex
-
We had a similar issues, the cause was a mixup of EA 6.5 and 7.0. The latter is much less verbose with DB.
A.S.
-
Hi Folks,
With the European support of EA we finally found the solution.
1. Upgrade Vista to SP1 - seems like some general issues are affected
2. If performance will not increase
change:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel
from 3 to 1
For me it works now :)
Cheers
Alex