8000 byte row limit blown while adding fields to Microsoft CRM Account object.

Hi all

My customer has requested a great deal of customisation on their CRM
implementation, particularly the Account object.

As such, around 40 new fields have been added to the account object
via the Deployment Manager.

Unfortunately, we are at the point now where additional fields cannot
be added, due to us reaching the 8000 byte row limit of SQL Server!

The message in the event log is as follows: 'dmLog: New size of the
attribute ({B806C9CD-554F-4BA6-80C2-0906640276BE}) exceeds the SQL
Server row limit of 8000 bytes.'

This really leaves us in a bit of a pickle, because:
a) We now cannot add any more fields to the account object.
b) We cannot undo, delete or modify any of the previously added custom
fields - they're stuck there (so we can't free up space that way)!

In short - we're stuck with what we've got and can't go forwards or
backwards.

Can anyone suggest any methods of working around this issue - as luck
would have it we are only one field short, but it's very limiting for
the future if we're stuck with this limit.

Andrew

Andrew Volz
Senior Consultant
Senetas Group

Phone +61 3 9820 1988 | Mobile 0409 795 537 | Facsimile +61 3 9821
4899
Level 1, 11 Queens Road, Melbourne 3004, Australia

John
Mon Nov 03 09:16:09 CST 2003

Sorry to say but you are stuck. You are not the first person to be caught
out by this problem. The only way out is a reload of crm to reset the
databases. Its a lesson but all users of CRM should backup their crm
databases so they have a copy of the initial database before they add
changes etc


"Andrew Volz" <volzy77@hotmail.com> wrote in message
news:4ff77a89.0311022217.624859f1@posting.google.com...
> Hi all
>
> My customer has requested a great deal of customisation on their CRM
> implementation, particularly the Account object.
>
> As such, around 40 new fields have been added to the account object
> via the Deployment Manager.
>
> Unfortunately, we are at the point now where additional fields cannot
> be added, due to us reaching the 8000 byte row limit of SQL Server!
>
> The message in the event log is as follows: 'dmLog: New size of the
> attribute ({B806C9CD-554F-4BA6-80C2-0906640276BE}) exceeds the SQL
> Server row limit of 8000 bytes.'
>
> This really leaves us in a bit of a pickle, because:
> a) We now cannot add any more fields to the account object.
> b) We cannot undo, delete or modify any of the previously added custom
> fields - they're stuck there (so we can't free up space that way)!
>
> In short - we're stuck with what we've got and can't go forwards or
> backwards.
>
> Can anyone suggest any methods of working around this issue - as luck
> would have it we are only one field short, but it's very limiting for
> the future if we're stuck with this limit.
>
> Andrew
>
> Andrew Volz
> Senior Consultant
> Senetas Group
>
> Phone +61 3 9820 1988 | Mobile 0409 795 537 | Facsimile +61 3 9821
> 4899
> Level 1, 11 Queens Road, Melbourne 3004, Australia