I don't have a spare TB to use for the initial file creation. On a different server I have 2+ TB available.

I cannot get a full backup using M$...

I understand what that file is, I just cannot gather why it could/would stop the restore on one machine and not the other?

That is my dilemma.

What was I thinking!

While I have been in this I have found another table that acts a builder / dependency tracker who's index is killing me.

Thanks...

OTTOMH # of updates is 1 to 5 to 10 depending on what the table is.

so from your response I'll stick with the rowlock?