I'm not 100% sure, but I don't think that matters.

The error I was referring to happens when you drop the PK to which the other table's FK's are pointing.

You end up getting a constraint error because, well... you're dropping a PK that has FK's pointed to it, and that's part of the job of constraints.

You would need to drop those other tables' FKs before dropping the PK on the table you want to move.

This is why I said, it's just not practical in reality without an outage.

~Craig