sharepoint truncates sysjobhistory (MSDB)

[aspijker]

Dear people,

We want to implement Sharepoint, but as a DBA I have some problems. Sharepoint has several jobs running every minute. This causes the logfile to be filled with sharepoint messages about the jobs. Now there is no history of my other jobs (from production databases). This is really unacceptable, so I need a way that either:
1) SQL only logs when a sharepoint job failes.
2) SQL doen not log any sharepoint job.

Is there anything I can do to stop this?

Regards, Aspijker

 

[SPV]

Couldn't you shift the SharePoint databases into a different SQL Server instance? Even if it's on the same server it would have its own MSDB database, so its own jobs/logs etc. I'm not sure of the licensing implications of a second SQL instance on the same server thought.

 

[aspijker]

Hey, good idea!
Just another thing that comes to my mind: is it easy to migrate the second instance to another server, later in the future?

 

[SPV]

I imagine it would be as easy as migrating to the second instance on the same server. Both would be an export/import operation within SharePoint, joining the web server to the new farm.