Forum Replies Created
-
AuthorPosts
-
AGA MediaMember'peterlaursen' wrote on '24:
OK .. we will have to try to reproduce that. How many tables and FK's do you have in that design? What server version are you connected to?
There are about 50 tables in that specific design and the server is 5.1.34 community.
AGA MediaMemberThank you both for your quick responses!
Sorry, but I can not provide my schema.
The server is 5.1.34 community and runs on localhost (no changes here during the upgrade from SQLYog 8.1 -> 8.2).
The delay occurs after calling upon a saved schema file and answering the second dialog (i.e. during synchronization to the tables).
Did as requested a comparison between 8.18 and 8.2 (on Win Vista Ultimate SP 2)
In both cases: first reboot, then call upon schema from file:
8.18: 2-3 seconds until the dialogs appear, then another 3 seconds until the schema is painted in designer
8.2: 2-3 seconds until the dialogs appear, then another *90* seconds until the schema is painted in designer (the time after the answering of the second dialog is not always as long as 90 seconds, but often around 60 seconds). Hope this will help!
Kind regards and a merry X-mas!
Joachim Bartels
AGA MediaMemberRight, it works! Thanx for your efforts!
Have a nice weekend, all the best,
Joachim Bartels
AGA Media
AGA MediaMemberMahesh wrote on Mar 12 2009, 11:54 AM:BTW: Which OS you are using ?We got it reproduced only in Vista that too with Specific DB's .
Hello, Mahesh,
I´m using Vista Ultimate SP1.
Thanks for your quick response.
Kind regards,
Joachim Bartels
AGA Media
AGA MediaMemberHello, Peter,
I can confirm the missing function (SQLyog Enterprise 8.03).
To reproduce: Call upon the Schema syncronisation, choose both the databases to compare, the button “Compare” is not active (s. att. screenshot).
Please come back if you need further information.
Kind regards,
Joachim Bartels
AGA Media
AGA MediaMemberYes, that would be fine or else display only the schema name on the tab with no ending at all.
Kind regards,
Joachim Bartels
AGA Media
AGA MediaMemberHi, Peter,
sorry for the confusion. Please see the attached JPEG for details.
As I mentioned before, all of the schema names end with “.schemaxml” which takes as much space (width) as the name itself on the tab.
So my suggestion was, to skip the ending and leave the name of the schema only on the tab – that's all.
Kind regards,
Joachim Bartels
AGA Media
-
AuthorPosts