This weekend I was preparing for a DW/Reporting demo at a conference next week. I know – I need to get a life!
I needed to quickly move data that I was generating on the CMDB side over to the DW and get it loaded up in the cubes. I didn’t want to wait on the scheduled jobs to run to move the data over. The tricky thing about these jobs is that they need to run in a certain sequence and they may already be in flight. I wrote a quick PowerShell script that will call all the right cmdlets in the right order and do the necessary status checking and waiting.
I’ve uploaded the script to the TechNet Gallery. Enjoy!
I was wondering if there was a log I can see why I keep getting:"Exiting since the job is an unexpected status".
I also get the same issue. Any time I run the script, at some point it just fails and closes with no explanation.