In Microsoft Dynamics CRM 2013, there has been a significant change to the database structure in that there are no longer EntityBase and EntityExtensionBase tables. Now there is just one entity table for a given entity. With this change, those who are upgrading an existing organization will eventually need to go through the process of merging the Base and Extension tables—either at the time of upgrade or at a later date.
As a result of this change, one of the issues that comes up while importing a CRM 2011 organization database to a new 2013 deployment (using the Organization Import feature of the Deployment Manager) is a table merge error stating: “This may exceed that the architectural limits of Microsoft SQL Server, and the merge operation will fail.”
The steps below will help you resolve this issue.
1. While importing an organization for upgrade to CRM 2013, the validation checks show the following error:
The fix is to decrease the number of columns in the source CRM system. This has to do with a view limitation in SQL server.
Note: Due to the architecture change, if you are hitting this limit ‘by just a little bit’, defer the table merge until later and try via the command line.
2. Cancel the import and defer the Table Merge in the following way, as noted in the CRM 2013 upgrade instructions:
How to Defer Table Merge
Install CRM, but do not upgrade any orgs.
Create a new reg key. Location: HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRMMergeBaseExtensionTables
Type: Dword (32-bit)
3. Restart import and complete.
4. At this point you need to find out what columns on that table can be deleted. Then you should be able to run the merge manually, as after the upgrade there will be a few less columns due to the new architecture of CRM 2013.
5. Follow the steps below using the merge tool that comes with the CRM 2013.
a. Set that registry key mentioned above in step 2 to 1 first (so CRM will run the merge).
b. Run the following statement at command prompt on CRM Front End server to merge the tables that have merge issues (the ones that stated issues in the import in step 1 above). Replace the names appropriately for highlighted parameters:
CrmMergeBaseAndExtensionTableTool /s:databaseservername /o:<databasename> /e:entityname /log:c:crmmergetoollog.txt
c. Repeat step 2 for all the entity tables with merge issue. The error in the import from Deployment Manager might still remain. In this case, run the rest of the merge for the whole database with the following command:
CrmMergeBaseAndExtensionTableTool /s: databaseservername /o:< databasename > /log:c:crmmergetoollog.txt
This should take care of the merge error, and importing the database should go smoothly at this point.
PowerObjects encourages customers to complete this merge as quickly as possible. NOT completing this step in the upgrade process may prohibit future updates.