Separate Application for Consolidation and Planning
Hi All,
Does anyone have the Consolidation and Planning in separate applications?
If so, what are the reasons for having them separate or what are the challenges.
Forum Discussion
Multiple reasons-
Huge data size, millions of records added every period.
Longer processing times on the SQL DB
For file based loads, one app ha sonly one harvest folder, this has been an issue as well.
Larger Data Units
Scalability issues, Performance issues when Consolidations and Planning tasks are running in parallel.
I believe even in OneStream book, they give an example of retail company with data volumes in millions of records and how splitting the application is recommended. I understand its theoretical but we do not see any benefits of having them both together in our current setup.
Also, we do not see any extensibility really being used.
I have few more factors as well, happy to discuss if anyone has really done the split or considered doing it.
The reasons you outline point towards a different instance (environment) rather than a different application, if separating the solution is desired. Two applications on the same instance share the servers and resources.
Millions of data records each period are being handled by customers in single applications, but of course each use case is unique (security, audit, process, data model, reporting / data storing requirements,...).
There are customers out there with a split, fingers crossed someone shares her / his reasons and experience.
Thank you for your prompt responses, Henning!
Looking forward for more insights on the app separation.