Hello Community,
I wanted to know about its efficiency when exporting complex SQL queries in Export SQL to Excel SS, as we have used this smart service to generate data for multiple sheets in excel, but if multiple people triggers the final parent process at the same time, it crashes the server, any one can guide to avoid that or any alternatives ?
Is there an issue with this smart service ?
Thanks in advance.
Discussion posts and replies are publicly visible
Can you serialize the execution of that export? Implement a queue to make sure that only a single export is running at a time.
yes we have implemented it in serialized way only inside the parent process (one Export filling one sheet at a time). It takes almost 3 to 5 mins to generate the output file , which is fine but it causes system crash if multiple requests are made for the parent process and which is likely to happen in real time scenario.
It is consuming too much of a heap memory for multiple instances !
Appian is not made to handle this kind of transformation intensive loads. Did you try to implement more logic in stored procedures and only do the final export using Appian? What is your use case?
And you will want to prevent any duplicate executions of this export.
Is that export depending on user input? If not, could you run it periodically and let the user just download a pre-generated file?
Thank you stefan for your inputs, I get your point there should be a mechanism which handles these type of requests smartly and effectively.