Thursday, November 21, 2013

Should we restart timer service after wsp deployment in production?

Hi,


We have already deployed a SharePoint timer job using feature activation during first release in the production. Now in the second release we are modifying some logic in the execute method of the job class.


Now after deployment of the timer job in the second release, do we need to restart the ows timer in production because of caching? During development we often have to restart OWS timer to clear the cache.


If we write restart OWS timer job in our deployemnet script for production, will that have any adverse effect on other timer jobs which will already running in the production?


Please help.


No comments:

Post a Comment