find out why they failed at the job logs? Anything curious in the server log?

in addition I would also export it to some text file(s) in case future sql versions won't support the old database format

The reindexing isn't a bulk operation.

I would try to make extra transactionlog backups during the indexing to keep the size small

*fingers crossed*

You can find those with

update ...

set myfield=left(myfield,1)+'xyz'+right(myfield,len(myfield)-4)

where myfield like '_abc%'

Are you working with sql authentication or integrated security (windows authentication)?

Are the servers up & running?

Could it be the new security settings for MSDTC in Windows 2003?

http://www.sqlservercentral.com/articles/Administering/debuggingmsdtcissues/1257/

See you then!

There certainly must be a script around for this.

Job history is maintained in the msdb database. sysjobhistory system table

Is the other side also windows 2003?

Is there a firewall in between?

This post mentions also another utility dtcping

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=455113&SiteID=1

just for future reference

dtstester: http://support.microsoft.com/kb/293799

Any chance that the other connecting machine isn't a windows 2003 machine?

In that case you need to set some security options for MSDTC.

Might find the kb back on monday.

there is a primary key on both sides?

The service pack setup is the same for client-tools and server.

Client version:

Open query analyzer

Menu Help -> About

You can find the various build versions of sql 2000 at

http://www.aspfaq.com/sql2000builds.asp

could be a mismatch in servicepack level between your client-machine and the server.

from the books online:

AUTO_SHRINK

When set to ON, the database files are candidates for periodic shrinking. Both data file and log files can be shrunk automatically by SQL Server. When...