On Thu, 31 Aug 2000, Claudio Valderrama C. wrote:

> Text types with expected length less than 30000 bytes can be stored as
> char/varchar fields in IB. In contrast, MsSql only allows around 8000 bytes
> in char/varchar fields. However, long string fields introduce a great
> performance penalty on IB, so the general solution is still to handle
> MsSql's TEXT as
> blob sub_type text in IB.

Regarding to migration issues it might be of great help to get
MS SQL type "text" converted into char/varchar for me. This would
probabbly solve all my problems. Your suggestion to choose an IB type
from a list if the wizard is in trouble would help very much.

> Probably, putting those fields in a script would render the script
> unreadable or extremely long. Also, they can't be inserted in IB with a
> literal value; you either use parameters or rely on loading first the
> f_StrBlob UDF.

May be the conversion of those fields would work and could be compared
afterwards with the comparison tool. I'm sure that a (readable) script is
the best in any case, but you can't have it in all cases, thought.

Kind regards

Andreas.