MYSQL Locationon shared server

[clarocque]

I am looking for information on the following:

I have several clients that use an opens source shopping cart (osCommerce) and I was wondering if it was a good or bad idea to create a seperate site on my shared server to host all off the mysql databases in one location.

My first thought of this was it would be easier to upgrade the databses and back them up. But then I started to wonder about:

Security - is it better or worse?
SSL - How will the store work on one account with SSL when the databses are in another site not using a SSL? Is it still secure?
Load time - will this speed up or slow down the store?
Does anyone have any thoughts or issues on this?

 

[sleipnir214]

I don't understand the question.

Are you asking about the location of the database backend for OSCommerce?

Want the best answers? Ask the best questions!

TANSTAAFL!!

 

[clarocque]

Sorry if it is confusing....

I am interested to know if the following is a good or bad idea.

I have several accounts using oscommerce on a shared server that I resell on.

Because I do all of the mysql management I was thinking that if I created another account on the server (myqldomain.com) and then directed all of my clients oscommerce stores to connect to the database on this account it would be easier for me to manage them (because they would al be in one location).

But I was wondering if I risk security: If I am using a SSL for the website store and it connect to the database (which is no longer localhost) is there a risk.

Also, would this make the site faster or slower by connecting a database located in another location.

And if anyone knew any pros or cons of doing this.

 

[sleipnir214]

I have managed multiple OSCommerce installations. I always used separate logins for each site -- managing MySQL logins isn't an arduous process, why make it easier for the hackers?

In terms of the location of the MySQL installation, localhost is fasted, because the client libraries don't use the network to communicate with localhost MySQL installations -- they use a form of interprocess communication. Move the MySQL installation to another physical server on the same network and it will be slower. But not by much -- just use IP addresses, not host names and a half-twist network cable to connect dedicated NICs. In exchange you get a more robust installation, as you have processors dedicated to tasks.

I recommend NOT moving MySQL to foreign networks.

Want the best answers? Ask the best questions!

TANSTAAFL!!

 

[clarocque]

Thanks - that gives me some insight...

Does it matter that this is all on a shared server ( I believe all databases are in the same mysql)

but how about preventing hackers.... that makes sense - do you still feel the sam if it is a shared server?