Closed JulianPayne-Align1st closed 1 week ago
Hi Julian, the most common cause of this type of experience is the TOM transaction is taking a long time. There can be various reasons for this like ongoing queries. Generally, if you wait, it will go through. If you want to confirm this is the cause and the issue is repeatable, you can - instead of committing the update by clicking the Update button - script it out to a TMSL script using the Script button - and run the script from SSMS. This is basically the same as what ALM Toolkit is doing, but it may provide a bit more diagnosis info by running from SSMS.
Hi Christian! Thanks for the quick reply :)
You are correct! I actually let the program run after is showed "Not Responding" and it eventually did succeed in updating. For reference this was a PBID (Source) on an Azure VM to PBIS (Target) via XMLA end-point.
I vaguely remembered having this issue previously on a former client project and could not remember if it was caused by a VM env issue, or some app option settings. But, I believe it was actually the same situation, it just takes a bit for the app to process the command.
If this persists, I will script it to TMSL, and then review in SSMS.
Keep up the amazing work, the schema compare capability is helping us immensely in our effort to automate our QA before we automate our deployments. We are using Process: Recalculate to just update the semantic (JSON) schema and keep the data, that way we can rapidly compare our actual numbers, after using ALM to review the schema changes at a meta-level.
My next task is to see if we can use ADO to pick up and process an ALMT file to push our model to our various environments (our Arhcitects want to use ADO v. native PBIS Pipeline tool).
THANK YOU
You're welcome!
ALM Toolkit freezes when we try to "Update". App freezes upon update action.
We are using an Azure VM. I can provide more details if needs be, but stability on our VM seems to be an issue.
Has anyone else reported the app not responding upon attemepts to update?