'#xp_results' table created in msdb.dbo.sp_get_composite_job_info procedure and temp tables are only session specific...

I think temp is getting dropped before reading it...

You may need to write your own procedure instead...

By design peer to peer does not have conflict resolution...

If you update the same row on both servers data will be wiped out by each other...

I don't think there will any issue other than authentication...

Best way would remove the subscriber before migration and once migrated to different domain re subscribe it...

    select *

        from msdb..MSagent_parameters 

        where profile_id = 1 

OR

you can right click the log reader agen and click agent profile...

Run the DBCC CHECKTABLE to check the corruption...

Some times rebuilding index will remove the corruption if the indexes are corrupted.

If reindexing not fixed the problem...

Run DBCC CHECKTABLE with repair allow...

Before changing the recovery model read the BOL topic RECOVERY MODELS because it is going to effect your database point in time recovery...

If you are disabling the auto update statistics...make...

Read the following KB article...

2007 time zone update for SQL Server 2005 Notification Services and for SQL Server 2000 Notification Services

http://support.microsoft.com/kb/931815

When some installs SQL 2005 on top 2000 all databases including using databases will be upgraded unless some detached user dbs before intalling 2005....

If the user database are upgraded to...

Even if the db is in simple recovery model, if the transaction is big you may run out of space sometimes if don't have enough space...

In the above mentioned scenarios...

In sql profiler/trace also you get the "system assigned id for a transaction"...

I don't think transaction ids from dbcc log and profiler/trace are the same...

Did you install SQL 2005 DTS addins "Microsoft SQL Server 2000 DTS Designer Components" on the server...

If not, install before running the job....

http://www.microsoft.com/downloads/details.aspx?familyid=d09c1d60-a13c-4479-9b91-9e8b9d835cdc&displaylang=en

Linked is one option for importing the data...

http://msdn2.microsoft.com/en-us/library/aa213275(sql.80).aspx

It is the only tool which checks HW and SW and database recomendations....

Read the following articles which will help you in your upgrade...

http://msdn2.microsoft.com/en-us/library/ms144256.aspx

http://www.microsoft.com/technet/prodtechnol/sql/2005/sqlupgrd.mspx

http://searchsqlserver.techtarget.com/generic/0,295582,sid87_gci1188595,00.html

Check this..

http://msdn2.microsoft.com/en-us/library/ms151174.aspx

This error is raised in transactional replication if the Distribution Agent attempts to update a row at the Subscriber, but the row has been deleted or the primary...

Critical Update for SQL Server 2005 Service Pack 2 (KB:933508)

http://www.microsoft.com/downloads/details.aspx?FamilyId=e2c358a1-ecc4-4c49-8f65-daa6b7800eec&displaylang=en