MS CRM Row Size Limit on Customizations

Fehler beim Anlegen eines neuen Schemafeldes. | hilpers

Fehler beim Anlegen eines neuen Schemafeldes. | hilpers — Tue, 20 Jan 2009 14:44:26 GMT

Pingback from Fehler beim Anlegen eines neuen Schemafeldes. | hilpers

Lipitor anxiety.

Lipitor. — Wed, 02 Jul 2008 01:45:56 GMT

Lipitor and zeita. Lipitor 40 mg. Lipitor generic. Benefits of lipitor. Lipitor. Lipitor side effects.

Lexapro.

Lexapro. — Sun, 29 Jun 2008 17:51:37 GMT

What are the side effects of lexapro. Lexapro. Lexapro sleepy.

re: MS CRM Row Size Limit on Customizations

Mads — Sat, 28 Aug 2004 11:34:00 GMT

Well, you definately have to get really creative if you want to use these xmlblobs for anything else than storage. Of course you can add the memo fields to forms, but they will display the raw xml.

re: MS CRM Row Size Limit on Customizations

Robert Eisenberg — Sat, 28 Aug 2004 01:17:00 GMT

How integrated can approach 3 be into the CRM forms and workflow. Can I add extra tabs and access some or all of the XML elements and attributes on them? Can I add some of the elements and attributes to existing forms if I want them placed on existing forms? Lastly, what about the workflow: Will I be able to use any of the elements and attributes to trigger workflows?

re: MS CRM Row Size Limit on Customizations

RayB — Thu, 19 Aug 2004 17:43:00 GMT

Not to throw more fuel to the fire, but the 'real' limit is actually much less than specified here. True, MSCRM/SQL will allow you to add up to the 8k limit, but if you have any hopes of using the Sales for Outlook client in an offline mode, it will fail if you are above 6k since SQL replication has a limit of 6k. Happy customizing all...

More on MSCRM Row size limitations..

TrackBack — Tue, 10 Aug 2004 11:52:00 GMT

re: MS CRM Row Size Limit on Customizations

KjellSJ — Sat, 07 Aug 2004 08:35:00 GMT

The SQL Server 8k limit is a poor excuse for bad application design for entity extension. It is not a good idea anyhow to allow e.g. the contact entity's ContactBase table to be extended with custom fields, because now MS cannot add a single new field to the next MSCRM version, without risking that a client's database cannot be upgraded due to no more room in the tables.

There are several other CRM systems out there, that allow virtually an unlimited number of extra fields, both on SQL Server and other RDBMSes. They do this by using separate extension table(s) for each entity. These other CRM systems that support this are e.g. Siebel and SalesMaker/growBusiness Solutions. Hey, even SuperOffice might support this better than MSCRM.

re: MS CRM Row Size Limit on Customizations

Mads — Wed, 04 Aug 2004 07:20:00 GMT

Well, at least they could have dedicated a customTable for each entity to, at the least, provide those 8k's.

re: MS CRM Row Size Limit on Customizations

Jay Nathan — Tue, 03 Aug 2004 19:00:00 GMT

The 8k limit on row size is a factor of SQL Server. 8k is the limit for a SQL Server row because data pages are 8k and rows cannot span pages. It is done this way for performance reasons.

The point remains, and is well taken that given the size of the built-in attributes of CRM entities, little room exists for customization...