Welcome back, for those who had read Part A of this blog, hope you would have tested Parallel Interaction and benefitted from it. For those who haven’t, you can read it at http://blog.octanesolutions.com.au/caveat-around-concurrent-data-loads-part-a
IBM has recently launched its Planning Analytics version 2.0.5 (on 25th June 2018); this article captures highlights of what’s new, improved and denounced.
I want to keep this blog very simple so that people who do not know the concept of blockchain can understand it. Target audience – anyone who can read English.
One of the most neglected and least prioritised activity among the grand scheme of development, in my opinion, is applying correct formats to data, both in cubes as well as standard web reports. In all fairness, if you’re one of my kind (occasionally-fall-into-a-slack type) who often miss out on this detail, then you have arrived at the right place. In my defence, I still feel that given the number of data points that one must apply formatting, it is only natural to miss a few, which then gets picked by business in live environment.
With users unceasingly (almost perennially) demanding higher data upload speed and concurrent transfers, this blog offers insight and considerations one should keep in mind while simultaneously executing a Turbo Integrator (TI) process. It also highlights steps to avoid TI looping and/or thrashing.
While working for a particular client project, I was asked to review an existing long running Turbo Integrator (TI) process and find out ways to optimise its processing time, without compromising on the business functionality.