Personalized Community is here!
Quickly customize your community to find the content you seek.
Have questions on moving to the cloud? Visit the Dynamics 365 Migration Community today! Microsoft’s extensive network of Dynamics AX and Dynamics CRM experts can help.
2021 Release Wave 2Discover the latest updates and new features releasing from October 2021 through March 2022.
2021 release wave 2 plan
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Community | FastTrack Program | Finance and Operations TechTalks | Customer Engagement TechTalks | Upcoming TechTalks | All TechTalks
I have requirement to update more that 1,00,000 records in CRM daily through batch job. Can anyone suggest, Which one is better approach, either Console Application or SSIS package. Batch should not take more than 6 hrs to finish. Please suggest any better approach with examples.
Two options you have:
1. SSIS package with help of some 3 party tool like KingswaySoft connector.
2. SCRIBE packages. -
Both options will serve you good... SSIS + KingswaySoft will be a cost effective option.. scribe is bit costly comparatively.
If found useful, please mark the answer as verified
I don't think there would be any significant difference between ssis and console application. The decision will be based on what is more comfortable to you i.e. are you more comfortable in SSIS or writing custom c# code. Perfoemance wise both will use crm service so no major difference. However if you need to selecct some data from a different source say some other sql server then ssis would be better as you can directly connect and extract your data where as in console you need to connect to db and then retrieve teh values.
Personally I would prefer SSIS over writing a console application if there is no major if else logic on update. If there is any complex business logic involved then I will go for console app.
Hope this helps.
As concern with time and performance, I can suggest you to use SSIS packages. Even if for complex business logic as well you can handle in SSIS using "Script Component".
Also you can create success and failed job list using packages.
Hi Balaji Karpurapu,
Based on my testing, there is a considerable difference in speed for this task between SQL Server Integration Services (SSIS) and console applications. I recommend using SSIS as it is faster, more reliable, and it is easy to schedule SSIS Packages to run daily with SQL Server Agent Jobs.
Business Applications communities