Tuesday, August 12, 2008
MOM 2005: How not to migrate your reporting databases
Great, the databases came up successfully.
Reporting, on the other hand, was not quite there.
Ok, next up, change the SCDW connection in Reporting itself to point to the new server. Great. The reports are there. *phew*
But the SQL services on the old server had been started again – damn MOM agent is too efficient *grin*. Stop the SQL services on old server, reporting is fooked. Ok. This one we know how to fix.
Run rsconfig again. Stop the MOM agent on the old server, then stop the SQL services. Ok, reporting works again, after having to assign an additional permission here and there. Or, I should say, we can run reports manually. Subscriptions are simply not there.
Fire up SQL on old server, export the jobs to a text file and run on the new server. Ok, goodie, this is starting to look better. Another permission tweak here and there. Now, we are almost in business. We can see the schedules – just still not sure if they are going to execute.
Who needs reporting anyway? This seems like a better idea anyway: