Exporting Connection Settings?

[dlumley]

Is there a way to export the connection settings from SQLYog? I am about to reinstall my laptop windows OS, if I can avoid it I really don't want to re-setup all the site connections…

Thanks in advance…

Dwane

[Ritesh]

Just take a backup of SQLyog.ini and restore it after re-insallation.

[dlumley]

Ritesh wrote on Dec 27 2005, 01:06 PM:

Just take a backup of SQLyog.ini and restore it after re-insallation.

[post=”8274″]<{POST_SNAPBACK}>[/post]

Well damn, slap me silly and call me susan! I did not realise it would be that obvious! I should have checked the dir for tihe ini file in the first place…

Thanks!

Dwane

[kuroi]

Ritesh wrote on Dec 27 2005, 12:06 PM:

Just take a backup of SQLyog.ini and restore it after re-insallation.

I know that this is going to be a really daft question … but where is the SQLyog.ini file?

A bit of background. Yesterday my SQLyog 612 stopped recognising my connections. I tried upgrading and am now running 614. My C:Program FilesSQLyog Enterprise folder has a sqlyog.bak.ini file which appears to contain all my configuration settings. But a full search of all my hard disks returns a null result for sqlyog.ini. I can rename the bak file to be this, but as soon as I restart SQLyog, it's named back to sqlyog.bak.ini and ignored.

[peterlaursen]

In recent version the .ini is located at (on WIN 2K/XP/2003) C:doc…s and settings{user}application datasqlyog

('application data' folder may have a localized name)

It was moved recently for Vista compability.

Please try copying the .bak.ini to that location and rename to .ini

It should all have happened automatically, but sometimes failed.

changelog details:

**************

6.07:

— Files used by SQLyog that are not read-only (.ini, .log, .err) are now no longer created in 'program files' files tree (or what localized name it has). The storage follows Microsoft recommendations for the various Windows versions. Existing files will be moved when program is started first time and a backup created in the original position. Windows Vista has actualized this.

6.08:

— If user's 'AppData' path used special characters (due to a localized 'AppData' folder or a user name with special characters) program was not able to access sqlyog.ini for read and write operations.

6.13:

— Empty or incomplete lines in sqlyog.ini would cause stop reading from the file. As a consequence details that could not be read would not be written. Those details that could not be read were lost.

I really hope that you did not come across a new issue … but first please try copying manually and report result.

I think it is the issue fixed between 6.12 and 6.13 you have experienced!

[kuroi]

peterlaursen wrote on Dec 14 2007, 01:30 PM:

Please try copying the .bak.ini to that location and rename to .ini

The manual copy worked fine Peter. And your hypothesis that the 613 update may have fixed the problem that caused it to go funny originally is looking well-supported by how well it's working now (I've tried and I can't break it again!).

Many thanks for your help.

[Author]

Posts