General discussion
Thread display: Collapse - |
All Comments
Start or search
Create a new discussion
If you're asking for technical help, please be sure to include all your system info, including operating system, model number, and any other specifics related to the problem. Also please exercise your best judgment when posting in the forums--revealing personal information such as your e-mail address, telephone number, and address is not recommended.
Question regarding MSSQL2000-warnings
I encountered a strange situation. I will try to explain it at my best.
I have a stored procedure. In it I create an unique index with the option IGNORE_DUP_KEY.The purpose is: if an insert is done with a new record, check if there is arecord with those values, and if there is then don't insert it, but do not generate an error. The stored procedure executes well(I mean all the transact-sql statements are executed, even if a warning appears).
That's fine. Now I created a job, in which I put a step that simply executes the previously described stored procedure. At execution the job shows me that it completed with errors (in fact in history I see that is about the warning, the error 3604, whihc I'm aware that it can appear, butthe stored procedure executes well).
Now my question: is there any way to make the job to execute well, but to not report error on the warnings, just if there are real errors.
(answers can be sent to xenon_je@hotmail.com)
Many thanks
Xenon