April 13, 2007 at 7:13 am
i have several dts packages, that insert/update data. as a means of preventing duplicate records i created a unique index and have it set to ignore duplicate keys.
sql 2000 sp3
the problem is that every time the job runs i get an email that the job has failed, when it really did not. someone had suggested installing sp4, but that is not feasible for us at the moment.
does any one know if there is work around, i was told i could try to trap the error message and then use that to determone what the message the is but, i need so me information on this
[font="Comic Sans MS"][/font]It is what it is.
April 13, 2007 at 10:06 am
Have you enabled package logging in the DTS package? That should tell you what error, if any, is generated when the package executes.
Greg
Greg
April 13, 2007 at 11:24 am
i have not tried that. but i will.
[font="Comic Sans MS"][/font]It is what it is.
April 13, 2007 at 11:28 am
but if i get the error, how do i get that passed to the job so that it does not give a failed job message.
[font="Comic Sans MS"][/font]It is what it is.
April 16, 2007 at 8:49 am
Maybe I misunderstood your original question. Do you want the job to succeed even if the step that executes the DTS package fails or do you want to figure out why the package fails?
Greg
Greg
April 18, 2007 at 9:48 am
o happy day. \
founf a work around on microsoft sql server, knowledge base. i have implemented this and it works like a charm.
FYI every one.
http://support.microsoft.com/kb/295032/en-us
[font="Comic Sans MS"][/font]It is what it is.
April 18, 2007 at 10:08 am
I'm glad you found a workaround. It's curious that the article says the problems was corrected in SP1, yet you still have it with SP3 applied.
Greg
Greg
April 19, 2007 at 6:52 am
i know and while doing same research, one of the solutions suggested is to install sp4, which we have not done becasue we run a our SQl in clustered environment and since we have no way of testing it, we were kind of stuck with sp3.
but this works really well. i have gotten any failed notices from those jobs, i checked them and it works quite well.
Oh, point of order:
i had to take the insert/update step out of the dts package and run it as the next step(using T-sql) in the job after the DTS STep.
[font="Comic Sans MS"][/font]It is what it is.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply