"bobhug" <bobhug@discussions.microsoft.com> wrote in message
news:A56C6840-13EB-40E3-8E5B-8060AA93FC00@microsoft.com...
> Hi!
> I am aware of http://support.microsoft.com/?kbid=842425 which covers the
> basics of how to move a Reporting Services database. I additionally
> understand about the RSEXECROLE role needing to be added to master and
> msdb,
> with the proper permissions granted, which this article does not mention.
> But how are people maintaining the schedules that have been created? It
> seems that it is necessary to move Reporting Services' SQL Server Agent
> jobs
> from the one server to the other, so that the schedules that have been
> created are transferred. Can someone recommend a way to do this?
>
> Thanks for any enlightenment,
> Bob

"Daniel Reib [MSFT]" wrote:

> If you are moving the DBs to a new server (not just renaming them), all you
> need to do is start the reportserver service. The service will see that the
> SQL Agent jobs are missing and populate them all. You will probably want to
> delete all the old jobs on the old server as well.
>
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "bobhug" <bobhug@discussions.microsoft.com> wrote in message
> news:A56C6840-13EB-40E3-8E5B-8060AA93FC00@microsoft.com...
> > Hi!
> > I am aware of http://support.microsoft.com/?kbid=842425 which covers the
> > basics of how to move a Reporting Services database. I additionally
> > understand about the RSEXECROLE role needing to be added to master and
> > msdb,
> > with the proper permissions granted, which this article does not mention.
> > But how are people maintaining the schedules that have been created? It
> > seems that it is necessary to move Reporting Services' SQL Server Agent
> > jobs
> > from the one server to the other, so that the schedules that have been
> > created are transferred. Can someone recommend a way to do this?
> >
> > Thanks for any enlightenment,
> > Bob
>
>