I want to know how to design and implement a procedure to preserve data integrity when upgrading a software
oluscoa
0
Newbie Poster
AskLeo
0
Newbie Poster
That's a huge topic. In the simplest case it's something like save old data, update new data and if ANYTHING goes wrong restore the old data. In the more complex case it starts to approach all the nuances of a SQL-style database's data commit - lock the data from being modified while it's being updated and be prepared to roll back to the original data should anything fail. The most important factors are the likelihood of some other application attempting to update the data while you're upgrading it, and your ability to roll back to your initial state on any error.
Perhaps you could share a little more of what you're attempting? Exactly what you need will depends on the specifics of the situation.
Leo
Be a part of the DaniWeb community
We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.