using 2005 management studio i made changes to an 8 step job on SQL 2000
server. I inserted a new step into position 8  and then tried to save it.
SQL2005 management told me that some feature was not supported on SQL 2000
so i pressed cancel. at this point both SQL 2005 management studio and SQL
200) enterprise management both report a 4 step job.

It is going to take me hours to restore the 8 step job from a backup so that
it can be re-inserted into the live DB.

what a fiasco.

Leon

Leon McCalla (leonmcca***@hotmail.com.junkfilter) writes:
That's bad. That would indicate that there is no transaction handling. I
think this is quite a serious bug. Please go to http://connect.microsoft.com
and file a bug for this. Try to be as specific as possible. Best if you
can give a complete scenario which reproduces the problem. (A two-step job
should be sufficient, I guess.) I know that this will take even more time,
but if Microsoft does not get to know about the problem, they can't mend
their ways.

Little Lock Symbols
lost sa password due to loss of employee
Backup using the proxy account in SQL2005
Scripting db creation
GoDaddy SQL Web Admin -- Importing CSV file