I'm the marketing guy, not the DBA. I want to begin collecting e-mail addresses for newsletters. My DBA is resisting an e-mail address-only database. How do organizations handle these data management issues? Any advice or resources we could turn to?
Chuck Kelley's Answer: Why create a separate database just for e-mail? You already have a database for your newsletters, so why not put a column in that database? Where do you collect the data now? If you are expecting to get these off the Internet, then other options are available, but you may have to pay for them.
Sid Adelman's Answer: A good rule of thumb is that you tell the DBA (or whoever you give your requests to) what you want, the data you need, the format, performance requirements, availability requirements, whether the data should be summarized and how it should be summarized (if at all) and the DBA figures out how to deliver it to you. Assuming the DBA can do a good job, you shouldn't be telling the DBA how to do the job. The DBA should provide you with the capability to access, query, extract or whatever you need to do against your e-mail addresses.
David Marco's Answer: I would be interested in the specific reasons why your DBA does not want to store these e-mail addresses in a database. You stated that you want an e-mail only database. Eventually, you will want to expand this to include more than e-mail addresses. I am the editor of a newsletter, and we certainly store our e-mail addresses in a database along with other various data.
Register or login for access to this item and much more
All Information Management content is archived after seven days.
Community members receive:
- All recent and archived articles
- Conference offers and updates
- A full menu of enewsletter options
- Web seminars, white papers, ebooks
Already have an account? Log In
Don't have an account? Register for Free Unlimited Access