> Any plan to just let SQL Server use TEXT/NTEXT?
Despite the fact that it's so slow?
Long story short: it was slow on a free edition; an update to the developer version
showed good results with TEXT and NTEXT (yes: usable respectively for strings
and unicode strings), BUT... it seems that TEXT and NTEXT types for some (to me)
unintelligible reason were deprecated in SQL Server 2005 and will be removed
in a future version.
I'll do some more research.
Very strange choice for a database, if you ask me. :-)