To properly test the new xMultiple support, you need to set the batch size to 20+. You could do something like 25, 50, 50, 100, or even 200. xMultiple is only enabled when the batch size is greater than 20, this is by-design, we might lower the threshold in future releases.
We have just made our 2023 release wave 2 available. Anyone wants to try out the new #xMulitple support and see how much performance improvement you get? Our preliminary tests show it is about 2 times faster, but I suspect that you can do better. #Dynamics365#dataload
In case you missed it, our 2023 Release Wave 2 is available now! This release brings over 290 new components, features, and enhancements to our SSIS Integration Toolkit product family. See more: https://t.co/JrOOne3rcX #SSIS#Components#KingswaySoft#ETL#DataIntegrationMadeEasy
In case you have missed it, our 2023 Release Wave 1 has been made available on March 17, 2023, which is packed with over 265 new features, updates, and enhancements, including 12 new APIs. https://t.co/WsE6NPtbad #KingswaySoft#DataIntegrationMadeEasy#SSIS#ETL
@ddlabar@kingswaysoft Bulk Delete is mainly designed for scheduled deletion. The feature name has confused most people. And it is intentionally engineered to be slow to protect the system, and as a matter of fact, it is awfully slow.
@ddlabar In contrast to what most #Dynamics365 developers believe, Bulk Delete is the slower version of deleting operation. If you want to have many records removed instantly, you'd use the Delete action. You'll need multi-threading to speed it up. @kingswaysoft can make a big difference
KingswaySoft's SSIS Productivity Pack has received the Google Cloud Ready - BigQuery designation, which certifies our solutions fulfill the core functional integration requirements. Read more! https://t.co/MYE4YKbZY9 #DataAnalytics#BigData#Data#DataScience#DataCloudSummit
@scottsewell@kingswaysoft Thanks Scott for bringing up the memory - I vividly remember the time at the Summit. Thank you for all your support throughout the years, particularly those creative suggestions. If I'm given another opportunity, I'd choose a different name for the dummy destination component. 😀
@adfcbiker@crmgustaf@kingswaysoft Good question. Those settings have been in our software for a few years. So yes, the optimization was baked in since we introduced the multi-threaded writing capabilities. For affinity cookies, we don't actually support those cookies from the beginning, so they are never on.
We are delivering two training sessions on SSIS development and our #Dynamics365 toolkit next week. Included in the training is a 30-day free access to our online training platform of the same content at https://t.co/9XoZh0okeQ. Sign up before the seats are sold out.
We are running two interactive training sessions on the topics of Foundation of SSIS Development, and Crash Course for #Dynamics365 Integration Toolkit. With the two courses, we take you from the ground up to a sophisticated D365 ETL developer. Sign up at https://t.co/soLWQgkZZ9
@peterbjorkmark@crmgustaf@KhanAli Someone in Microsoft should fix the writing. I get the points they try to make, but this recommendation doesn't stand in court. I believe using batch is beneficial for performance. I agree we should be gentle with the setting, use a batch size of 10 so we don't push hard on them
@peterbjorkmark@crmgustaf@KhanAli Thanks Peter for sharing the experience, appreciate it. I agree with your assessment earlier, I believe Microsoft recommends not using batch for the same reason that they don't want all the loads to get processed on the same server, which affects the serviceability of the server.