> I've recently started getting the following error when I retrieve
> long text entries from my MS SQL Server database...
>
> "Cannot sort a row of size 8150, which is greater than the allowable
> maximum of 8094"
>
> I have one column in one of the tables involved in the SELECT statement
> that has a maximum of 8000 characters.
>
> Should I resize this column to 7800 or similar, to avoid this problem,
> or should I modify my SELECT statement to ignore the errors and proceed
> as normal?
>
> Thanks.
> --
>
> fiddlewidawiddum

On Fri, 14 Apr 2006 ML <ML@discussions.microsoft.com> wrote:
> Do you have to order by the full length of 8000 character column? Maybe
>
> left(<colum>, 2000)

On Fri, 14 Apr 2006 ML <ML@discussions.microsoft.com> wrote:
> Well, post the query then, so we can have a look.
>
> Sorting is done implicitly by the Query Optimizer when GROUP BY or DISTINCT
> is used in the query.

On Fri, 14 Apr 2006 ML <ML@discussions.microsoft.com> wrote:
> Judging by the simplicity of the query, I guess the problem originates in the
> execution plan. Try this:
>
> SELECT TOP 6 d.EntryTitle, d.EntryText, d.EntryDate, l.LocName, c.CountryName
> FROM Diary d
> inner join Location l on d.idLocation = l.idLocation
> inner join Country c on d.idCountry = c.idCountry
> ORDER BY d.idDiary desc
>
> Here I've used the contemporary join syntax that may help the Query
> Optimizer to build a different execution plan.

"Stimp" <ren@spumco.com> wrote in message news:slrne3u0f8.vf.ren@carbon.redbrick.dcu.ie...
> I've recently started getting the following error when I retrieve
> long text entries from my MS SQL Server database...
>
> "Cannot sort a row of size 8150, which is greater than the allowable
> maximum of 8094"
>
> I have one column in one of the tables involved in the SELECT statement
> that has a maximum of 8000 characters.
>
> Should I resize this column to 7800 or similar, to avoid this problem,
> or should I modify my SELECT statement to ignore the errors and proceed
> as normal?
>
> Thanks.
> --
>