SQL Server allows 8k per data page. If you have an int column (4 bytes), you
still have almost 8,000 ansi characters to work with. This is not enough for
the verbose, however, which forces you to use a Text field:
CREATE TABLE ArticlesForTheReallyVerbose
(
ArticleID int IDENTITY(1,1) PRIMARY KEY
, ArticleText text NOT NULL
)
You might think you can separate out the text into multiple fields, ala:
CREATE TABLE ArticlesForTheReallyVerbose
(
ArticleID int IDENTITY(1,1) PRIMARY KEY
, ArticleText1 varchar (7000) NOT NULL
, ArticleText2 varchar (7000) NOT NULL
)
... but you will go over the page size if someone actually is verbose.
There are pitfalls with text fields, but this case calls for one.

Signature
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
***************************
Think Outside the Box!
***************************
> Hello,
>
[quoted text clipped - 16 lines]
> a better DataType to hold the information? With MS Access this is a major
> problem but I would expect that but not with SQL Server? Any suggestions?
Dam6 - 19 Aug 2005 11:47 GMT
Thanks!!!
> SQL Server allows 8k per data page. If you have an int column (4 bytes),
> you
[quoted text clipped - 44 lines]
>> problem but I would expect that but not with SQL Server? Any
>> suggestions?