beware: SQL2005 management studio not 2000 compatible

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 (leonmccalla@.hotmail.com.junkfilter) writes:
> 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.
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.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

Best way to migrate SQL version 7 databases to 2000

We are moving all databases from a SQL version 7 server to a version 2000
server. Which of the following is the preferred method?

1) Detach the DB on the version 7 server, move it to the new server via
Windows Explorer and reattach it there.

2) Use SQL Enterprise Mananger with the DTS Export Wizard to "copy objects &
data between SQL server databases" from the version 7 server to the 2000
server.

With the changing of the version, I thought maybe option 2 is best. Thoughts?

--
Mike Czizek
Iowa Network Services, Inc.
mikec@.netins.comConsider using backup-restore method. It works rather well.

--
Dean Savovic
www.teched.hr

"Mike Czizek" <Mikec@.netins.net> wrote in message news:bnts03$5b8$1@.ins22.netins.net...
> We are moving all databases from a SQL version 7 server to a version 2000
> server. Which of the following is the preferred method?
> 1) Detach the DB on the version 7 server, move it to the new server via
> Windows Explorer and reattach it there.
> 2) Use SQL Enterprise Mananger with the DTS Export Wizard to "copy objects &
> data between SQL server databases" from the version 7 server to the 2000
> server.
> With the changing of the version, I thought maybe option 2 is best. Thoughts?
> --
> Mike Czizek
> Iowa Network Services, Inc.
> mikec@.netins.com