I'm very confused here.
Now - I'm not a DBA - but this procedure seems to me - at least - to be doing the exact opposite of persistence testing.
In a 'Verse where X ships exist after spawning due to player invoked activation - and testing the persistence of said ships by resetting the "spawn ownership" of players Y to dislocate from spawned entities - database 1 cannot be persistent as it depends entirelly upon resets from database 2 to reach it's initial state to persist from.
Now - I'm not a DBA - but this procedure seems to me - at least - to be doing the exact opposite of persistence testing.
In a 'Verse where X ships exist after spawning due to player invoked activation - and testing the persistence of said ships by resetting the "spawn ownership" of players Y to dislocate from spawned entities - database 1 cannot be persistent as it depends entirelly upon resets from database 2 to reach it's initial state to persist from.