Very long rich text information - datatype?

[John Clark]

Sorry if this seems a little basic, but I'm putting together an application
where large amounts of text will be required in a single record - way more
than 8000 characters.

What's the normal way of coping with this? Splitting into multiple records
each with a max of 8000 chars?

Thanks,

JC

[Adrian Edwards]

Look in BOL at text and ntext.
John Clark wrote:

Sorry if this seems a little basic, but I'm putting together an application
where large amounts of text will be required in a single record - way more
than 8000 characters.

What's the normal way of coping with this? Splitting into multiple records
each with a max of 8000 chars?

Thanks,

JC

[Ross Presser]

> John Clark wrote:

Sorry if this seems a little basic, but I'm putting together an application
where large amounts of text will be required in a single record - way more
than 8000 characters.

What's the normal way of coping with this? Splitting into multiple records
each with a max of 8000 chars?

On Fri, 17 Sep 2004 12:08:12 +0000 (UTC), Adrian Edwards wrote:
Look in BOL at text and ntext.

And consider keeping your text in files on the filesystem, with filenames
kept in the db. Not perfect for every app, but suprisingly good in many
cases - and moves load from the db server back to the app or OS where it
belongs. :)

(And consider not top posting :))

[John Clark]

"Ross Presser" <rp******@imtek.com> wrote in message
news:11****************************@40tude.net...

John Clark wrote:

Sorry if this seems a little basic, but I'm putting together an
application
where large amounts of text will be required in a single record - way
more
than 8000 characters.

What's the normal way of coping with this? Splitting into multiple
records
each with a max of 8000 chars?

On Fri, 17 Sep 2004 12:08:12 +0000 (UTC), Adrian Edwards wrote:

Look in BOL at text and ntext.

And consider keeping your text in files on the filesystem, with filenames
kept in the db. Not perfect for every app, but suprisingly good in many
cases - and moves load from the db server back to the app or OS where it
belongs. :)

(And consider not top posting :))

That's something I'm looking at right now - seems like it might be the best
way for my app.

Thanks for the responses !

JC