Put `text` column in another table?

[howachen@gmail.com]

Hi,

usually, use of a single table is recommended for performance as only
one seek time is required. However, when a table include many columns
with `text` field, should we also do this?

Should be separate the `text` fields in another table, and link them up
using a key?

Which method is better for performance?

Thanks.

[Jerry Stuckle]

[email]howachen@gmail.com[/email] wrote:

> Hi,
>
> usually, use of a single table is recommended for performance as only
> one seek time is required. However, when a table include many columns
> with `text` field, should we also do this?
>
> Should be separate the `text` fields in another table, and link them up
> using a key?
>
> Which method is better for performance?
>
> Thanks.
>

It depends on a lot of factors. Number of columns, size of the data in
those columns, frequency of which you're accessing columns and probably
30 other things I can't think of right now. It's totally impossible to
provide a general rule.

For instance - at least in MySQL - if you have a column containing 1K of
text (average) and you need it on a 75% of your requests, you *probably*
want it in the same table. But if that column contains 1M of text
(average) and you only need it on 2% of your requests, you probably want
it in a different table.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
[email]jstucklex@attglobal.net[/email]
==================