I am working with an inherited Commercial-off-the-Shelf (COTS) application that uses SS2K. I know from the BOL for SS2K that regardless of the data type, rows are limited to am maximum of 8,060 bytes. I found an article at SqlServerCentral where the author narrowed that down to 8,046 with 14 bytes for overhead.
Our application has a "forum" feature where users can leave messages. Since this application is used in a "language education" environment, the character sets used are not all Latin so the field that contains the body of the message typed NVARCHAR (max 4000 Latin chars).
Now my group has been approached and asked to design a work-around so that the users can exceed the 8,060 byte limit.
In my mind, I can imagine that we would have to come up with a design where the message text can occupy multiple rows in a table. I am thinking that we would have to manage pointers and row continuation flags, etc.
Q1: Has anyone seen a stored procedure or process that would be a suitable workaround?
Q2: If so, did the designers of the system handle the extended row by using code in the front or back-end?
Q3: Can anyone point me to an example on the web that describes such a design or where I can get some advice for this predicament?
Thanks ahead of time for any help you can provide!