[Ritesh]

He He.

Thank you 😀

[Ritesh]

Erik wrote on Nov 25 2004, 11:43 AM:

Ritesh wrote on Nov 25 2004, 11:39 AM:

Congratulations BTW 😉

:huh: :huh:

[Ritesh]

It is because we are now using a new client library.

We are working on this issue and plan to fix it in 4.1.

[Ritesh]

I think we had fixed a similar bug in SJA 4.0.

Are you still facing problems in the 'live' setup (client = 4.1.7, server = 4.0.21) with the latest release?

[Ritesh]

I was just wondering how is it going?

[Ritesh]

I have forwarded the issue to my development team.

If it is in FREE edition, it will be in Enterprise version also.

[Ritesh]

We are working on this issue.

Your idea about the problem with 'timestamp' is correct 😀

Quote:

After I've came to the conclusion that syncing mysql 3.23 to 4.x didn't work

Can you tell me the problem you are facing?

[Ritesh]

Currently, this feature is not available in SJA.

[Ritesh]

I am not sure if I understood your problem. Can you explain it a little more?

[Ritesh]

In the connection window there are two tabs: Server and Tunnel.

In the server tab, enter the following details.

MySQL host address: A host name where the database is situated or the IP address of the server.

User name: User name for connecting to the database server. Note: This is MySQL username. Not your FTP or webserver username.

Password: MySQL user Password

Databases: Database name. You may enter several database names separated by semicolon (like db1,db2). If you do not enter the database name, all the database names would be listed, to select from.

Port : A TCP/IP port for connecting to the database server.

In the tunnel tab, enter the following details:

Username: Username to access the SSH server.

Password: Password to access the SSH server.

SSH Host: Address of the machine on which SSH server is running.

SSH Port: Port on which SSH server is listening. By default, it is 22.

Localhost: The value will always be localhost and is readonly. This is because SQLyog creates the SSH port forwarding option on the local machine only.

Local Port: The local port on which SQLyog will listen locally for correctly port forwarding MySQL requests. Note: If you are connecting to two or more different MySQL servers, then you need to provide two different local port values in the respective connections.

To understand the setup better, let us connect to a MySQL server using a real life example.

E.g. Your website is hosted on 234.56.65.78. This server also has SSH server running and listening on port 22. Your MySQL server is located on server 234.56.65.79. This machine only allows connection from localhost or machine within the same network (e.g. 234.56.65.78). You publish your website on 234.56.65.78 using the username and password provided by your ISP. ex. the username and password provided is ssh_user and ssh_pwd respectively.

In this particular case you have to put in the following value for various options:

Server Tab

MySQL Host Address: 234.56.65.79

Username: Your mysql user name.

Password: Your mysql password.

Database: The database that you want to connect to. You can leave this field blank.

Port: The port MySQL is listening. By default it is 3306.

Tunnel Tab

Username: ssh_user

Password: ssh_pwd

SSH Host: 234.56.65.78

SSH Port: 22

Local Host: This is always localhost.

Local Port: Any port that is unused on your local machine. If you dont have a MySQL running on your machine then you can provide 3306.

[Ritesh]

SQLyog is a client application like notepad and cannot be used from a web-browser.

phpMyAdmin is a web-based application and is meant to be used from a browser.

Quote:

to my understanding the program is there, but it also goes through the web

I guess you are talking about HTTP Tunneling which is completely different. HTTP Tunneling saves your day if your ISP/MySQL provider disallows remote access, either my blocking the MySQL port or by giving access to “localhost” only. SQLyogTunnel.php provided with SQLyog Enterprise exposes the MySQL C API as web-services allowing you to enjoy all the cool features of SQLyog.

For more information on how to use HTTP Tunneling, just press F1 in the connection window.

[Ritesh]

After 2.51, we have added many new features like:

• SSH/HTTP Tunneling
• Database Sync
• ODBC Import
• Notification Services
• and much more

For a complete version history check out http://www.webyog.com/sqlyog/whatsnew.html

[Ritesh]

Have you tried SQLyog's SSH/HTTP Tunneling features?

[Ritesh]

It should.

I have forwarded the issue to my development team.

[Ritesh]

As I can see, http://www.xy1234.co.uk is hosted on a machine having IP: 212.257.125.28.

Are you sure you are giving the correct password for sxxn user? Also can you check out whether the user sxxn has correct permission to access database db73723452.

[Author]

Posts