tew
Ten Centuries
Points: 1249
More actions
March 5, 2009 at 11:02 am
#954222
I would speculate that the host was memory constrained.
Amy Herold
SSC Rookie
Points: 34
March 5, 2009 at 11:30 am
#954242
This issue was resolved by re-creating the job. Apparently the job itself had somehow become corrupt and that is why it was executing twice. Created a new job from scratch and this was no longer an issue.
Steve Jones - SSC Editor
SSC Guru
Points: 728159
March 5, 2009 at 11:39 am
#954250
Thanks for the update and solution. That shouldn't happen often, but it's good to consider removing and recreating the job.
Follow me on Twitter: http://www.twitter.com/way0utwest Forum Etiquette: How to post data/code on a forum to get the best help My Blog: www.voiceofthedba.com
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply