[Brendon Kozlowski]

Without having explicit knowledge of SQLyog's installer's process, a registry cleaner and traversal of the local drive that you installed it to should do the trick.

Locate where you installed SQLyog (mine is at C:Program FilesSQLyog) AFTER doing the uninstall. If the directory is gone, then all you really have to worry about now are registry keys (as DLLs are safer to leave on the system than remove anyway). If not, just delete the folder.

Many people suggest CCleaner as it's extremely powerful (and free). I use TweakNow Registry Cleaner. Either should work just fine, and TweakNow has a free version as well.

Running one of these programs and clearing out your registry should “clean” any remaining registry entries that aren't needed by your system anylonger. Always be careful when messing with the registry though, it's usually a good idea to create a backup before removing anything, just in case.

Getting back on the subject:

– Did you do as Ritesh suggested? Did you copy the sqlyog.ini file from the install of the FREE version to the install directory of the PRO version BEFORE uninstalling?

[Brendon Kozlowski]

If you can compile your own version, all source code is publically available via MySQL's Subversion server:

http://dev.mysql.com/tech-resources/sources.html

I don't think I'm allowed to redistribute the file that I found which was linked to according to the license, but I don't have that computer nearby to tell for certain. Sorry. Goodluck with Visio. I hope your database structure isn't too big. 😀

[Brendon Kozlowski]

Direct Link: http://forums.mysql.com/read.php?113,44108,44108

I've used it a little bit. It's better than DBDesigner4 was (in my opinion), but that's to be expected, whether it's a bit buggy or not.

You've been busy with that FAQ, Peter. Good job. I've been waiting for the GUI builder for SQL log so that I can print out the database schema in a nicely formatted manner to use as documentation, without having to go back and create it (and any changes I made if I originally made it) in Visio.

[Brendon Kozlowski]

bin-log creates which logging type? I just opened up my MySQL “Developers Library” book and started looking at the backup/transaction logging types…

I've found –log-bin which is the binary log.

I'm not seeing the explicit command for the binary update log…are they one in the same?

–log is the general log file.

The configuration file is the my.conf file, correct?

…back on topic, I still think this feature would be great. 😀

[Brendon Kozlowski]

…I knew MSSQL didn't like a certain comment character, I thought it was /**/, guess not. Anyway, thanks for the quick research and confirmation of the double newlines.

[Brendon Kozlowski]

peterlaursen wrote on Feb 13 2006, 11:52 AM:

What is the particular reason for the 2nd request?

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

I know that MS SQL doesn't like the /**/ form of commenting, and although I haven't tested Oracle or PostgreSQL, I would assume that at least one of them wouldn't like it either. The double hyphen is just more standards acceptable in SQL, I believe.

I *think* phpMyAdmin would also get confused with commenting such as this, and if, say, I emailed a backup to someone who prefers to use a different MySQL client, it's possible that this style of commenting could confuse the client and cause problems.

…and yes, I noticed the double newline problem due to my text editor (Crimson Editor) showing an “unknown” character, which usually shows up as a filled square (such as xDB, or character 219 in decimal). I had problems with a poorly created CSV file and had to clean it out, so I created a function that prints out all character codes of a given text file and used that to determine that there are two carriage returns in a row, with a line feed after.

[Author]

Posts