Re: Ignoring Errors
- From: "Tibor Karaszi" <tibor_please.no.email_karaszi@xxxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Apr 2005 19:28:30 +0200
OSQL is better than Agent TSQL as OSQL doesn't terminate on errors. However, for some errors, *SQL
Server* terminates the batch. I suggest you check out the articles on error handling at
www.sommarskog.se.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<googlemike@xxxxxxxxxx> wrote in message
news:1113236973.134465.132330@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I have some "best effort" jobs that try at various times to walk over
> missed records from one system to another about 5 times. After that,
> the data becomes stale and is no longer usable, so I have another
> process that comes after that to investigate the problem.
>
> The problem I'm having is that when my best effort jobs ran in MS SQL
> Server, they would run and then bomb out immediately. I want it instead
> to just continue on error.
>
> Meanwhile, I then switched the jobs to osql.exe and Task Scheduler this
> weekend. The results were exactly the same -- the job dies on error.
>
> Can you help me figure out a way either for osql.exe to continue on
> error, or for me to ignore all stored procedure errors and just keep on
> continuing?
>
> I'm used to VB's "on error resume next" and unfortunately I don't see
> one in MS SQL Server. This is absurd!
>
.
- References:
- Ignoring Errors
- From: googlemike
- Ignoring Errors
- Prev by Date: Re: Ignoring Errors
- Next by Date: connecting to outlook form
- Previous by thread: Re: Ignoring Errors
- Next by thread: connecting to outlook form
- Index(es):
Relevant Pages
|
