Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
dhochstein1962
Starting Member
2 Posts |
 Posted - 2008-08-21 : 10:54:01
|
We are moving from SQL 2000 on one server to SQL 2005 on another server. Our DBA converted over the DTS packages and jobs to the 2005 server to look like 2000(legacy). Our series of jobs we run every month end to load our data warehouse are set to utilize alerts to start the next job once the current job is done. The last jobstep of our jobs look something like this, RAISERROR (50045, 1, 1), where 50045 is an alert set up to execute the next job. When I am trying to test our jobs out on the new box, I am unable to get the jobs to initiate execution of the next job. I have looked at the alerts and they seem to have been converted as expected. Does anyone have any ideas what needs to be fixed so one job can kickoff the next job using alerts in SQL 2005 after converting from SQL 2000??  |
|
|
dhochstein1962
Starting Member
2 Posts |
Posted - 2008-09-16 : 08:34:25
|
| I eventually found that my problem was I needed to have the "with log" command after the RAISERROR (50045, 1, 1) command. Once the 'with log' was added, the next job was initiated from the alert and all was well. SQL 2000 didn't require the 'with log' to be present where as SQL 2005 evidently does. |
 |
|
|
|
|
|
Using alerts to start the next job