21.02.2015, 11:50
If you have arleady used normalization on your database, then structurally speaking each system should have their independent tables with the respected primary and foreign keys.
In that case, the option I see here is to update the database according to changes. More often than not, a lot of the data you update everytime is not required to be updated because they haven't been altered. I don't even know how you could possibly have so much data to update that your database/server crashes, but assuming this is the case, my option seems to be the solution I can think of.
Also, while on that subject, I'd advise you to port to a plugin that supports multiple threads, so that your server is unaffected when the database requires a long time to process the queries.
I hope this helps.
PS: Have you considered you might have another issue?
In that case, the option I see here is to update the database according to changes. More often than not, a lot of the data you update everytime is not required to be updated because they haven't been altered. I don't even know how you could possibly have so much data to update that your database/server crashes, but assuming this is the case, my option seems to be the solution I can think of.
Also, while on that subject, I'd advise you to port to a plugin that supports multiple threads, so that your server is unaffected when the database requires a long time to process the queries.
I hope this helps.
PS: Have you considered you might have another issue?