From: andrew on
A colleague has sent me a text saying, "it's a SQL bug, when a row gets too
close to the max row size".

"andrew" wrote:

> Hi Razvan, thanks for your reply. We are not actually using replication, but
> it was worth the suggestion.
>
>
> "Razvan Socol" wrote:
>
> > Hello, andrew
> >
> > I have a feeling that this may be related to replication.
> > Is replication enabled for this database ? If yes, what type ?
> >
> > Razvan
> >
> >
From: andrew on
Still puzzled - we have done a check on rowsize and no rows get much beyond
3000 bytes - nowhere near the max row size.

"andrew" wrote:

> A colleague has sent me a text saying, "it's a SQL bug, when a row gets too
> close to the max row size".
>
> "andrew" wrote:
>
> > Hi Razvan, thanks for your reply. We are not actually using replication, but
> > it was worth the suggestion.
> >
> >
> > "Razvan Socol" wrote:
> >
> > > Hello, andrew
> > >
> > > I have a feeling that this may be related to replication.
> > > Is replication enabled for this database ? If yes, what type ?
> > >
> > > Razvan
> > >
> > >
From: Tibor Karaszi on
I didn't memorize the error message, but to me it sounded like some external component was involved.
Anyhow, did you try the ROBUST PLAN query hint?

--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi


"andrew" <andrew(a)discussions.microsoft.com> wrote in message
news:261B007A-9D74-453C-98F3-7FBBA5F543C8(a)microsoft.com...
>A colleague has sent me a text saying, "it's a SQL bug, when a row gets too
> close to the max row size".
>
> "andrew" wrote:
>
>> Hi Razvan, thanks for your reply. We are not actually using replication, but
>> it was worth the suggestion.
>>
>>
>> "Razvan Socol" wrote:
>>
>> > Hello, andrew
>> >
>> > I have a feeling that this may be related to replication.
>> > Is replication enabled for this database ? If yes, what type ?
>> >
>> > Razvan
>> >
>> >

From: Erland Sommarskog on
andrew (andrew(a)discussions.microsoft.com) writes:
> Still puzzled - we have done a check on rowsize and no rows get much
> beyond 3000 bytes - nowhere near the max row size.

But maybe a row in a temporary work table could? (One that SQL Server
creates behind the scenes.)

Tibor's suggestion for ROBUST PLAN seems to be on the mark. ROBUST PLAN
instructs the optmizer to make sure that the maximum row size can fit.

--
Erland Sommarskog, SQL Server MVP, esquel(a)sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
First  |  Prev  | 
Pages: 1 2
Prev: How to update a bitwise column
Next: Query help