Easy, import / DTS the legacy information into your new DB schema and
utilise Meta information to allow for searching capabilties - storage and
processing should never come into it - if the DB is well designed along with
the code; then the server should simply be doing its job - serving.
as for normalizing; with a globally designed DB - it is not necessary; the
logic is ported into the App.
believe me, try it and you will see a difference :-) I am not advocating
that we throw away Codd altogther, far from it - in some cases; a
'traditional' DB is the only way but for the web the ability to syndicate
etc is paramount.
N
as for this not being appropriate n a CF Talk forum, I disagree - some of
the worst mistakes by CF coders is badly designed DB's.
<!-----------------------------
Neil Clark
Senior Web Applications Engineer
Spectra / CF / XML
MCB Digital
Premier Macromedia Partner
Tel: 020 8941 3232
Fax: 020 8941 4333
e-mail: [EMAIL PROTECTED]
---------------------------->
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
