Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-07-21 : 09:41:43
|
| Gerard writes "Hi there,I need to write a web based email manager type application, which basically enables the import of email lists and lets you edit/delete/etc. The email lists, of course, will be used for sending out emails using a mail server.Easy enough, but I'm not sure the best way to store the data. As it's only a single field that's required 'EmailAddress', I can't decide whether it should all be stored as a flat file or add an EmailAddress table to the application SQL Server database. The main issue I have is the potential quantity of email data to be stored. Some users may import hundreds of thousands of email addresses, perhaps even a million or so, and am wondering if all that data, potentially used just for a few mail shots, should be stored seperately to the main app.Anyone any ideas?ThanksGerard" |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-07-21 : 10:36:46
|
| That sort of quantity shouldn't be a problem for sql server - more of an issue is how you want to manage the daat.You could bcp the data in from flat files when you want to use it and bcp it out again after editing. You could also just leave it in a table.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
datagod
Starting Member
37 Posts |
Posted - 2006-07-21 : 11:50:44
|
| You sound like you work for a spammer. If you do, please stop. |
|
|
|
|
|
|
Storing Email addresses Flat File v SQL