January 11, 2017 at 11:42 am
I'm dealing primarily with SSRS 2012 integrated with SharePoint 2013.
Given SSRS databases participate in a SQL Availability Group and the SSRS Service Application is restarted after a failover event. Additionally the SSRS agent jobs on the now secondary node are deleted. SSRS rebuilds its sql agent jobs after the restart. Likewise using SharePoint backup and restore capability to DR the service application also causes the same result.
In either of these situations I see the SQL Agent jobs get created with the original Start Date specified by the user. Due to the way the SQL Agent works, if these are weekly or monthly schedules at the very least, the schedule is wrong.
I've simulated this by creating simple jobs and by adjusting when the start date and observing when it's scheduled to run next.
Have any of you automated the correction of the subscription start dates after these events in your environments?
Viewing 0 posts
You must be logged in to reply to this topic. Login to reply