The sp_fulltext_catalog stored procedure will be removed in a future version of SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use...

You can't backup the db without replication info including replication properties...

When you restore the db other than the server which was backed up sql server removes replication but not rowids...

It is better to qualify the object name with owner name..incase if you have two objects with same name and different owners...

exec sp_changeobjectowner @objname =  'owner.object' ,  @newowner =  'owner'

exec sp_changeobjectowner...

You can use tsql instead VB script use rename and copy the file...

exec xp_cmdshell 'rename \\servername\c$\filename.zip filename_new.zip'

exec xp_cmdshell 'copy \\servername\c$\filename_new.zip \\servername\d$\filename_new.zip'

If you want to use in DTS execute...

If you want use DTS then check GLOBAL VARIABLES option...

OR

You can do the BCP in combination with xp_cmdshell using tsql too...

Yes, you can do it using dts package and can be scheduled too...

In your DTS you should drop and recreate tables in Excel other wise by default sql appends the...

When are you getting this error? Can you explain...

If you don't have 2005 components then how you access the server?

Remove the subscription and delete the triggers from subscribed table...

If there are no other subscriptions in that db then run sp_removedbreplication procedure...

Resubscribe and see what happens.

I did 600+ GB backup to network share and still doing using third party backup tools without any issues..

I am using multiple backup files to improve performance...

Yes you can monitor ddl changes using ddl triggers but in 2005 not in 2000...

Check SQL server 2005 BOL

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

Check this...

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

Did you check this article?

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

Use the corsor or while loop to do this or

you can use undocumented extended procedure xp_execresultset procedure to do this...

If procedure was corrupted then how you were able recompile it?

I think your procedure was using incorrect execution plan ... recompilation forced to generate new execution plan...

Check BOL...

How to: Create a Subscription for a Non-SQL Server Subscriber (Replication Transact-SQL Programming) 

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