On the 'Advanced' tab of the 'Job Step Properties' you can play with the 'on failure' and 'On Success'.
Ex:
step 1_DO_MY_THING
on success : quit with success
on failure : go to step 2
step 2_REPORT_THE_FA ILURE
on success : quit with failure
on failure : quit with failure
In other cases you could merge the steps or save the state somewhere in your db
Jogos
Last Activity: Mar 16 '07, 02:51 PM
Joined: Mar 16 '07
Location:
-
For my knowledge it isn't possible to change that limit. You should split your table or in some cases use Ntext-type but that would generate a lot of other troubles.Leave a comment:
-
1
As in previous reply you can shedule a job on a frequent basis and check the time and quit when not met, you wil have to mark something when job has run.
2
You can use the msdb.dbo.sp_add _job procedure to shedule the job on the time you want, for example the time which comes from somewhere in your database.
Be aware that once created the change of your data will not have implication on the sheduled job.Leave a comment:
-
You should use LEFT JOIN but be aware when you will use a WHERE-clause on the 'not present' items
Info from books online (the guide in troubled moments!)
Joins can be categorized as:...
Inner joins (the typical join operation, which uses some comparison operator like = or <>). These include equi-joins and natural joins.
Inner joins use a comparison operator to match rows from two tables basedLeave a comment:
No activity results to display
Leave a comment: