Hi aLTeReGo,
appreciate you taking time to provide input. I had opened a case during our extremely long SAM upgrade. It was support who told me that there were other customers who had experienced same, and to wait it out. Support did mention that there were specific SAM db/table changes as a result of going 5.0 -> 5.5 that were major contributing factors. I am now planning our SAM 5.5 -> 6.0 upgrade, and organizational management are asking me if I can reassure them that same outage will not repeat. As per your suggestion I altered our SAM data retention from 7 days detail / 30 days hourly / 90 days daily TO now read 1 day / 7 days / 30 days respectively. I also took a snapshot of current database tables (row counts & sizes) to see effect when next nightly runs. I am aiming for SAM 6.0 upgrade on Dec 11th, but only if I'm able to reassure management we won't experience same outage. Our orion platform manages network for majority of British Columbia, our usual maintenance window of 2hrs has been working out very well, until that last SAM upgrade