SQL Server – How to Change Job Output Log Location Using Ola Hallengren’s Scripts

ola-hallengrensql server 2014

When using Ola Hallengren's SQL Server Maintenance Solution, the job output log is going to a local directory on the SQL server. I was thinking of placing these logs on a fileserver to allow access to more people so they can review the job output.

My questions are:

  1. How can I change this location?
  2. Is there any downside to changing the location?

Thanks!

Best Answer

I’m going to reword your questions a little:

Q: Should I log Agent jobs directly to a remote file server? No, because if you lose network connectivity or the file share goes down, your Agent job could fail. Your Agent job might not require network connectivity, like an update stats job, so that failure would suck.

Q: If I want to centralize Agent job history, how should I do it? Consider logging to a table (and Ola’s scripts support this too.) That way you can centralize the data in whatever method you like, like replication or log shipping. I like logging to a DBA utility database, and then restoring that from all my servers to one central server daily. Then I use union all views to combine the data from all my servers. It’s not up to the second, though.