Clever, but I don't recommend doing this at all. You are really risking getting things really screwed up! You are better off just scripting out replication including the jobs, removing it totally (sp_removedbreplication and the jobs), detaching, attaching, and just running the replication script again..It is a little longer, I know but alot safer in the long run..The problem with clever little shortcuts like this is they can fill volumes with what they don't tell you can go wrong! Don't gamble with your databases with cute little workarounds like this. You will probably regret it sooner or later. Stick to what has been tried, true, and tested. DBA's that start experimenting with things like this usually find themselves looking for another job...trust me I have seen it far too often.
Travis Lee Alltop
Sr. SQL Server DBA
It is a good Solution for Moving Replicated Databases
I understand your position, but its just a matter of mitigating the risk isnt it? Aside from that, what do you think could go wrong with this approach?
"I ran into this a couple years ago..."
Nice solution, but it was discussed on this forum three years ago and you may remember this topic...
Why not just back up the database and restore it to the new location? You don't have to touch the system tables then.