For your own sake, listen to AgentM for he knows whereof he speaks.

What I'm seeing at a glance from your diagram is, at the minimum, three tables with an unknown number of fields per table. Database normalization seems rather simple, but it gets complicated the larger the database. In fact, I think it would be safe to say that I have met MANY programmers who know SQL and database programming like the back of their hands yet don't know anything about database design.

Trust me, you don't want that data in a single field.

Oh, and welcome to Perlmonks :)

Cheers,
Ovid

Join the Perlmonks Setiathome Group or just go the the link and check out our stats.