I have a large (>40 million rows) table that currently consists of a few
integers and a varchar. I need to add a memo (text > 255 chars) field to
about 2% of the rows. Originally I was going to create another table with a
key and the memo field, but this method is complicating the programming
logic. The easiest solution would be to add the memo field right to this
table, and use it only when needed.
Does the presence of a memo fields affect the performance a lot? Are memos
stored with the records themselves, or in a separate part of the table data
(I believe Access and SQL-Server stores the memos separately, which can kill
performance).
Finally, in this case should I allow Null's and use them for the 98% empty
fields?
Thx,
Tac
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
