My team now has several beta clients using our product. The current method of updating the client database to the latest version consists of reinitializing the database and re-creating the client configuration manually, which is not so much, but certainly tedious and will change as we implement some kind of migration strategy.
My question is, can I use a span (or some other tool) to control the migration of the database schema of all instances of our product, but save the data of independent instances? What is the best approach to this problem.
source
share