LOL I don't envy my whole existence! Let alone job which includes being off ill with a serious illness yet still called upon to "help" the person who manages the servers (but doesn't know anything about SQL or code - just networking and building computers etc) and the person he would normally have asked was not there.

So no I don't envy it. But it is now done.

I used that script, ignored the Fk errors and then just went into each job "of mine - let the other owners of their DBS sort their own jobs out!) and added in the scheduled and target server option.

It just seems like it should be such a simple thing to fix but I could find no mention of a TargetServers column in any of the tables. I thought if I just ignored any schedule inserts if a record already existed with that ID then that would solve the FK issue but it just meant no schedule part was added so I was obviously still missing something like someone said earlier.

I thought maybe the target servers thing was down to the MSDB DB knowing the data being inserted was from "another server somehow", there were some columns where you had to insert the server name which I replaced with @@servername but that didn't seem to fix it.

Anyway thanks and any ideas let me know!