List:General Discussion« Previous MessageNext Message »
From:Jason Pruim Date:August 23 2007 4:37pm
Subject:Re: Database architecture and security
View as plain text  
On Aug 23, 2007, at 11:28 AM, Rolando Edwards wrote:

> Think about how your going to make backups.
>
> 1) Would you backup one database with all the mailing lists together ?

If I went the route of 1 database, Many tables, I would just backup  
the entire database and all the tables in one shot. Unless I"m  
misunderstanding how MySQL handles the backups, I would think that it  
would preserve the individual tables?


> 2) Would you keep the backups of each user separate ?

I probably should, but hadn't thought that far ahead yet. Still  
working on getting the PHP Scripts and everything else set.

> 3) Could users ask you to restore mailing lists from the past ?

The only reason I could see them asking for that is if they went  
through and deleted the entire database, which has to be done  
manually, meaning you have to hit "delete" on each record to delete  
it. I would hope they would realize what they were doing before going  
through the entire database...

>
> You could make one mysqldump for everybody from one database if
> no one ever asks for restoration of past mailing lists.
>
> You could create a database for each user.
> Then, backup (mysqldump) each database for each user.
> Should they request a restore, it's becomes an easy thing.
>
> How you answer the three questions I posed should help you decide.

I am starting to lean towards the multiple databases with 1 table  
even though it makes more files on my server, I think it gives me the  
most flexibility/security. That way I can also edit 1 database and  
not screw it up for the entire user base, just the one user :)



>
> ----- Original Message -----
> From: "Jason Pruim" <japruim@stripped>
> To: "MySQL List" <mysql@stripped>
> Sent: Thursday, August 23, 2007 10:58:52 AM (GMT-0500) America/ 
> New_York
> Subject: Database architecture and security
>
> Hi Everyone,
>
> Just had a quick question about a database I'm working on.
>
> I am planning on having the database open to customers of mine to
> store their mailing addresses on-line, and be able to manage the
> records.
>
> Is it safe, to have 1 database with lots of tables? Or am I safer
> setting up separate databases for everyone?
>
> I should mention, no one will be accessing the database directly,
> it'll be through a web interface and php to display it.
>
> Any info would be greatly appreciated!
>
>
> --
>
> Jason Pruim
> Raoset Inc.
> Technology Manager
> MQC Specialist
> 3251 132nd ave
> Holland, MI, 49424
> www.raoset.com
> japruim@stripped
>
>
>
>
> -- 
> Rolando A. Edwards
> MySQL DBA
>
> SWMX, Inc.
> 1 Bridge Street
> Irvington, NY 10533
> (914) 406-8406 (Main)
> (201) 660-3221 (Mobile)
>
>
> -- 
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql? 
> unsub=japruim@stripped
>
>

--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424
www.raoset.com
japruim@stripped


Thread
Database architecture and securityJason Pruim23 Aug
  • Re: Database architecture and securityRolando Edwards23 Aug
    • Re: Database architecture and securityJason Pruim23 Aug
  • Re: Database architecture and securityGary Josack23 Aug
    • Re: Database architecture and securityJason Pruim23 Aug
  • Re: Database architecture and securityDavid T. Ashley23 Aug
    • Re: Database architecture and securityJason Pruim23 Aug
      • Re: Database architecture and securityDavid T. Ashley23 Aug
  • RE: Database architecture and securityJerry Schwartz23 Aug
    • RE: Database architecture and securityWm Mussatto23 Aug