You could always make MatCodeID an Identity field and not worry about it.

Alternately, you can try something like this

INSERT INTO TableB (MatCodeID, MatCode, MatDesc)

I am from Sunny, Hot & Humid Durban, on the East Coast of South Africa.
I have never crossed the pond, but I may have an opportunity to attend some...

I would use a linked server from each server to the shared server, and create a view that references the remote table across the linked server.

Now use the view...

Ed's idea of a new persisted column is your best bet.  You can then even  index the column for better performance when seraching.

But, it seems like you are...

Just guessing here, but it would seem that all of your data is coming from views.  Without any knowledge of the underlying sources for each view, I would take a...