ignore errors

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Andrea Anastasescu (anastasescu_a_at_yahoo.com)
Date: 11/19/04 

Date: Fri, 19 Nov 2004 15:02:01 +0200

Hi to everybody,

To formulate my question in a short manner, I'd like to ignore errors.

I start a job inside an update trigger.
When I make quick updates from Enterprise Manager's interface, it returns
the error that the job is already started etc (there could be something else
also, e.g. the sqlAgent is not running) and the update is not operated.
When I make the same quick pdates using directly TSQL, there are mesages
corresp. to the errors occured, but the uodates are operated to the
table-data.
What should I do in order to make the updates from the Enterprise Manger's
interface too.
I mention that the kind of errors I want to ignore are not critical (e.g. if
the SQLAgent is not started thi do not mean a critical error).
What is the reason of the different behavior of issuing the operatoins from
TSQL (query analizer) and the Enterprise manager->open table->return all
rows ?
I'm thinking of how an update issued by an application connecting through
ADO, or ODBC or DBLib will behave?
Thank you in advance,
Andrea