Changing packages in sql 2005 vs sql 2000 and jobs

[timscronin]

In sql 2000 if you created a dts package and then scheduled it life was good. however if you went back and changed the dts package and saved it the job that runs the DTS would run the original package, not the changed one. In sql 2005 I created a maintenance package to dbcc all db's and optimize all db's. I went in and noticed that 2 new db's I had created were not included in the "generate tsql from the package" I did a refresh and now they are included. My question is, I saved my changes, now under sql 2005 will the new package be run or the original version?

 

[mrdenny]

SQL 2005 runs the package via the Job Name not the version GUID so the job should run no problem.

SQL 2000 will run the correct version of the job, provided that the job is setup to run the package by the package name or the package guid. If you have it run it based on the package version guid (which it shouldn't do by default) then only a specific version of the package will be run.

The generated T/SQL may be cashed in your client. Check the servers ERRORLOG and see if the databases were being checked. The generated T/SQL box shows that the T/SQL shown may not be the actual T/SQL that is executed on the server.

Denny
MCSA (2003) / MCDBA (SQL 2000) / MCTS (SQL 2005) / MCITP Database Administrator (SQL 2005)

--Anything is possible. All it takes is a little research. (Me)

http://www.mrdenny.com