Issue with a split dedi

So I have a server hosted on a shared dedi that was split. Issue is, one of the other users uses mysql and has mysql installed on the dedi. I want to keep my database completely separate and private from any one else on the dedi. I tried installing mysql on my portion, but it caused problems for the other user. Any ideas on how I can successfully keep my database private, without any other dedi user accessing it?

MySql runs as a service and on a specific port.
You could try reinstalling it, under a different name, and a different port (if given the option).
Default port is 3306 now.

Quote:

Originally Posted by Aceking MySql runs as a service and on a specific port. You could try reinstalling it, under a different name, and a different port (if given the option). Default port is 3306 now.

Tried reinstalling, but not as a different name. Would it matter what name? And I tried running it off port 3310, since the other user was using 3306.

Yeah the name matters, because that is what it makes its Service name.
So if you both have the same service name, I can see issues occurring.

Is the dedi running windows server? I assume 2008 R2.

If so, Start>Administrative Tools>Services

You will see your MySql instance in there.

Quote:

Originally Posted by Aceking Yeah the name matters, because that is what it makes its Service name. So if you both have the same service name, I can see issues occurring. Is the dedi running windows server? I assume 2008 R2. If so, Start>Administrative Tools>Services You will see your MySql instance in there.

Thanks to this post I got through the first step of my problem. Now the problem is, the other user is using a MySQL Connector/Net prior to version 4.0, while I have the most recent version. It seems to me that my server is trying to use the other MySQL instance. I don't really see where I would change it to my instance.
For example if I'm not being blunt enough, Start->AdminTools->Services "InsomniaMySQL" then there's the default "MySQL".

If its all installed and running as intended then you need only change the connection string in your source code/config file to point it to the correct instance.

If you can't see your service running on the server then you haven't installed it correctly.

Quote:

Originally Posted by Aceking Yeah the name matters, because that is what it makes its Service name. So if you both have the same service name, I can see issues occurring. Is the dedi running windows server? I assume 2008 R2. If so, Start>Administrative Tools>Services You will see your MySql instance in there.

Quote:

Originally Posted by Korvacs If its all installed and running as intended then you need only change the connection string in your source code/config file to point it to the correct instance. If you can't see your service running on the server then you haven't installed it correctly.

Yup yup, this was the issue. I just needed to add Port=3310; to the connection string, and it was all good to go. Thanks Jack and Ace!