Hello list,
I'm currently developing a newsletter tool allowing customers to send
their newsletters to their clients and get all kinds of statistics. For
each customer of ours, I need to save up to five different lists of
newsletter recipients with their email addresses and some other stuffs
our customer wants to store. Furthermore I'll be saving all sent
newsletters (only the templates) over half a year. At the moment, we
only got a few thousand customers but this design should be fit to serve
a lot more.
Let's assume we got 20,000 customers with 2,000 newsletter recipients
each. That'd make some 40,000,000 recipients to be stored in our
database and some 520,000 newsletters each half year providing that they
send one each week. Well, I was thinking of putting them all in one
giant table and associating them with the different lists. That way one
person might actually be very redundantly saved in our database. And, I
presume, it'd take a while to gather the information relevant for a
customer. So, I've been thinking of maybe saving the lists as txt-dumps
and importing them into a temporary table when needed. Or, well, I'm
stuck here. Since I've never dealed with tables that big I'm not exactly
what you would call a performance specialist.
Maybe one of you has already designed a similar database or an idea of
how it could work. Any ideas welcome!
Thanks for reading
Dan
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
