My client has software installed at hundreds of locations that uses a SQL Server db. Of course, everyone is on a different version of the software and thus the db as well. At install time, we need to update the target db from a current version db. The current version db will have all the tables, columns, stored procs, etc. and if any of these are missing from the target we need to add them. In some cases when a new table moves, the data must move as well so we need a way to indicate this.

I know EF Migrations can do something similar. Is that the approach to take? We don’t need to move any source code as the source will be updated already and we are installing a new EXE/DLL set at the client which needs to have whatever changes are needed to bring their db up to the current version.

What is the best way to handle this?

Thanks

Carl