hmm...I still get about 4 error logs about duplicate keys....I do not have a clue. How to extend the log viewer that more data is put from the scheduler?

I started having performance issues and found that GetSchedule and GetScheduleNext stored procs were taking almost 90% of the database server processing time. With some research and information found here, I identified my problem. The Job "DotNetNuke.Services.Scheduling.PurgeScheduleHistory" started erring (database timeout) about a month ago. I had set it to run once a day and apparently that was not enough. Once it started erring the ScheduleHistory table started growing. Since the retry is also set to a day, the process would only try once a day and it would timeout every day.  The table got pretty large (~100000 rows) and that caused the two stored procs to take longer than they should ( I did run the tuning adviser also and the indexes were fine) . To fix the problem I created a database job that used the same code as the PurgeScheduleHistory stored proc (with a slight alteration). I found that I could delete around 200 of them in a few seconds so used this script and set the schedule to run once a minute (I did this to throttle the cleanup and not impact performance on the production server):

DELETE

top (200) FROM dbo.ScheduleHistory

FROM