sql server - Best way to store emails for historical/review purposes -


I have a service that processes the email in the mailbox and once processed, something in the database in the database The schematic stores the information in minutes:

  • ID
  • Sender
  • Topic
  • Body (Parsed The result of being /
  • The date

I am creating a web front-end for the database and the main purpose of archiving email Provide convenience for users, look back and see what they sent. However, another reason is for my auditing purposes at the end.

Currently the email is being moved to specific mailbox folders. So what I'm planning to start, once processed on email, record it in the database and record delete instead of deleting the email from the mailbox. Switch to.

Question delete ...

1) the actual email you exchange is a good idea? Is it better in the case of buses ?
2) To keep the size of the field I was removing HTML out of email, is it a bad idea? Should I just store e-mail because it has been received?

Any other advice / suggestions would be great.

In both cases, I think you should catch the original email. Storage is cheap, but if the disk space is really a problem, then look at the compression rather than sort it out to solve it.

Both of your usage cases (historical records and audits) can not be completely completed. Email in the database Once you start tampering with the data, though by removing the "bus" formatting It becomes difficult to prove that you have not edited it in another, more important way, especially if you have removed the original email instead of storing it.

You do not say which business you are in, but the other thing is whether there are active data retention policies within your organization or compliance in the broad jurisdiction is going down every time.


Comments

Popular posts from this blog

oracle - The fastest way to check if some records in a database table? -

php - multilevel menu with multilevel array -

jQuery UI: Datepicker month format -