If you mean that it is locked then run sp_who2 to check if while executing the command another process is locking the table.

You must put the sentence into a variable for example:

DECLARE @cmd AS VARCHAR(100)

SELECT @cmd = SELECT * INTO ' + @temptable_1234 + ' FROM pubs'

EXEC (@cmd)

Remember that the diff backups, holds all the changes since the last full backup. Everytime you execute a full backup, SQL set a flag in every page in the data...

Did you create this script with profiler? or you manually created it? Wich what user are you running the sp?

The password shoudn't be written to the job.

You should check the script that you are running, that doesn't print the sa password.

What type of replication?

If you can stop the server, you can deattach the db, copy it to the desire location and then re attach it.

If not possible, you wan't be able to move...

Did you already run a checkdb in the database? If not, do it and tell us if it shows any errors at the end.

I would still use replication. I would use transactional replication and use it with internet. Check in BOL or ask here to know how to set up replication-

NExt time you kill the spid , run kill [spid] with statusonly, and that will show you the rollback process. If it shows that is has reached 100% and that...

To know the count of the indexes you can query the table sysindexes and search for the indexes of that table where indid between 2 and 254.

You can execute:

SELECT * FROM TableName

WHERE LEN(BarCode) = 14

you can view the transaction log with a third party tool call Log Explorer.

You can check it at http://www.lumigent.com

But you can also trace your server to check all the transactions...

Do you have access to the disk on that server?

Wich owner do you have in the job?

Does it change after the miscellaneous agents runs?

Wich SQL version?