SQL Server Error whilst creating new attribute

I've previously added a good number of custom attributes
the Lead entity type, however whenever I try a add a new
attribute since I receive the an error telling me that the
attribute addition has failed and to check the Event Log
for more information.

In the Event Log is two related error events:

(the first)
dmLog: New size of the attribute ({FEC5CEBE-B6F3-4E3C-90E9-
B1A1CB2333F5}) exceeds the SQL Server row limit of 8000
bytes.

(second)
dmLog: Failed to add new String attribute
(CFSCL_ACCOUNTS_InvoiceType) to Lead entity.

I've googled this error message and found a Microsoft
resource page -
http://support.microsoft.com/default.aspx?kbid=832753

However I don't think the information contained on the
page relates specifically to this problem - there is a
software update there, but it is for MSCRM v1 rather than
v1.2 (which is the version I'm using). But I think that
v1.2 should already includes this update.

Can anyone shed any light on whats going on here. I
presume that the creation of the new attribrute is trying
to create one or more new records/fields in the Metabase
which SQL Server is unable to do and hence generating the
error; does anyone out there know how to work around this?

Cheers, Paul.
Xchange Group.

Paul
Mon Aug 02 11:59:19 CDT 2004

Ouch.. God only knows why that limit wasn't mentioned in
the MSCRM Architecture Exam..

Anyhow, cheers for your help mate. I think I'll try and
workaround using Memo fields or somesuch, right pain mind.

>-----Original Message-----
>You've blown the limit. See earlier postings in this
forum or my weblog posting at
>http://weblogs.asp.net/mnissen/archive/2004/08/02/205135.a
spx
>
>I'd also really like to get feedback on my "hack options"
described in that post.
>
>chrs,
>mads
>--
>http://weblogs.asp.net/mnissen
>
>
>"Paul McQuillan" wrote:
>
>> I've previously added a good number of custom
attributes
>> the Lead entity type, however whenever I try a add a
new
>> attribute since I receive the an error telling me that
the
>> attribute addition has failed and to check the Event
Log
>> for more information.
>>
>> In the Event Log is two related error events:
>>
>> (the first)
>> dmLog: New size of the attribute ({FEC5CEBE-B6F3-4E3C-
90E9-
>> B1A1CB2333F5}) exceeds the SQL Server row limit of 8000
>> bytes.
>>
>> (second)
>> dmLog: Failed to add new String attribute
>> (CFSCL_ACCOUNTS_InvoiceType) to Lead entity.
>>
>> I've googled this error message and found a Microsoft
>> resource page -
>> http://support.microsoft.com/default.aspx?kbid=832753
>>
>> However I don't think the information contained on the
>> page relates specifically to this problem - there is a
>> software update there, but it is for MSCRM v1 rather
than
>> v1.2 (which is the version I'm using). But I think
that
>> v1.2 should already includes this update.
>>
>> Can anyone shed any light on whats going on here. I
>> presume that the creation of the new attribrute is
trying
>> to create one or more new records/fields in the
Metabase
>> which SQL Server is unable to do and hence generating
the
>> error; does anyone out there know how to work around
this?
>>
>> Cheers, Paul.
>> Xchange Group.
>>
>>
>.
>

Matt
Mon Aug 02 17:58:58 CDT 2004

Paul,

The limit you are hitting is actually a SQL limitation. The KB article you
found refers to a bug that occurrs when importing schema info in CRM, not
actually adding them via Deployment Manager.

Basically, SQL will not allow a row to span a page (hence the 8k limit).
Problem is, CRM treats the record as if every field is filled to the max
(varchars only take up space for the actual data). Many of the fields in the
stock app are rather large and take up a lot of that 8k limit.

SQL will actually allow you to continue to add columns, but warns you of the
problem. It's not an issue until you try to save more than 8k of data. At that
point, the update errors out. Once you get to the pint of maxing out, CRM won't
allow you to add any more. They opted to prevent an error occuring that would
bubble to the end user that would result in lost data.

It's kind of a hassle, but that is what's happening.

Matt Parks
MVP - Microsoft CRM

----------------------------------------
----------------------------------------
On Mon, 2 Aug 2004 07:12:15 -0700, "Paul McQuillan"
<paul.mcquillan@xchangegroup.com> wrote:

I've previously added a good number of custom attributes
the Lead entity type, however whenever I try a add a new
attribute since I receive the an error telling me that the
attribute addition has failed and to check the Event Log
for more information.

In the Event Log is two related error events:

(the first)
dmLog: New size of the attribute ({FEC5CEBE-B6F3-4E3C-90E9-
B1A1CB2333F5}) exceeds the SQL Server row limit of 8000
bytes.

(second)
dmLog: Failed to add new String attribute
(CFSCL_ACCOUNTS_InvoiceType) to Lead entity.

I've googled this error message and found a Microsoft
resource page -
http://support.microsoft.com/default.aspx?kbid=832753

However I don't think the information contained on the
page relates specifically to this problem - there is a
software update there, but it is for MSCRM v1 rather than
v1.2 (which is the version I'm using). But I think that
v1.2 should already includes this update.

Can anyone shed any light on whats going on here. I
presume that the creation of the new attribrute is trying
to create one or more new records/fields in the Metabase
which SQL Server is unable to do and hence generating the
error; does anyone out there know how to work around this?

Cheers, Paul.
Xchange Group.