tag:blogger.com,1999:blog-5472436831307966815.post4433058930042072489..comments2024-03-20T00:30:07.883-06:00Comments on Daniel Cai's Blog: Presentation on Enterprise Data Integration for Microsoft Dynamics CRMDaniel Caihttp://www.blogger.com/profile/05461949321689249420noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-5472436831307966815.post-9845055711069781272013-04-09T14:09:35.395-06:002013-04-09T14:09:35.395-06:00Thanks Garry! When you write to CRM in parallel, t...Thanks Garry! When you write to CRM in parallel, the best strategy is probably to write to one entity at a time. When you write to different entities in parallel, there is a greater chance that you run into generic SQL errors, particularly if those entities have relationship involved. <br /><br />Also, the CRM team has made some improvement that reduces the chance of general SQL errors, so you might want to stay updated with more recent rollups if you are using CRM on-premise. <br /><br />Thanks again. Daniel Caihttps://www.blogger.com/profile/05461949321689249420noreply@blogger.comtag:blogger.com,1999:blog-5472436831307966815.post-10642928905105664522013-04-09T12:43:08.015-06:002013-04-09T12:43:08.015-06:00Nice presentation for your first!
Our problem is ...Nice presentation for your first!<br /><br />Our problem is that when we go parallel, we get generic SQL errors when we start doing inserts/selects/updates at about 3-4 parallel processes from various entities!<br /><br />Basically, SQL server cannot handle the parallel load to a particular xxxx_MSCRM db!<br /><br />Any options other than getting better hardware?Garry Lindsayhttps://www.blogger.com/profile/05358426709686284049noreply@blogger.com