Jump to content

Recommended Posts

Posted

I have customer data that I want to keep in a mySQL database, but also worry about a script (such as a forum script) having a flaw which could potentially let a hacker get access to those DB's (either directly, or through being able to view files or scripts which contain the password).

 

The best solution I've been able to think up is to store the customer database on a separate server hosted by TCH. The only problem is that customers need to verify their order number to gain access to a customer area of the site - which means that some data from the database needs to be on the "public" server. This would probably require some automated way to "sync" a table of the database across two servers.

 

Another option would be to have two separate databases - one with "private" information (like full customer detail) and the other "public" (well, at least accessible) data which the script can access and verify against. Then, whenever an employee makes a change to the customer data, or inserts/removes a customer in the "private" database, do the same thing for the "public" database. This could potentially have synchronization issues since it would be possible to modify each database independantly.

 

Do any database experts have suggestions on the best way to implement this type of thing?

 

Thanks!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...