Search Results

I assume when you fix the bug first, you will also release a new version of the application before the migration is completed (otherwise the whole question would be pointless). … Based on this assumption, ask yourself: What is the nature of the bug, and what will it mean to your users when you leave it in the application for the time of migration? …

The SP may also remove itself once it was executed successfully, to leave the DB in a state as if the data migration was done by an ordinary SQL script. …

, there is MigrationBuilder.Sql as the tool for handling any kind of complex migration. … For such cases, this Stackoverflow Q&A demonstrates how to get direct access to the database context during a migration, which is all one needs to implement arbitrary C# code which runs as part of migration …

The only way to reduce the risk of breaking things in production is to test new releases before deployment. Fullstop. And if your budget for testers is small, try to create as many automatic tests as …

On Stackoverflow, you can find examples like this one showing how this can be done in Laravel directly inside the up method of a migration. …

So it seems you are planning to rewrite the original application step-by-step and replace it with a new application. Depending on the application logic, a "step-by-step" approach maybe possible or not …

don't think it is possible to measure that beforehand, because it depends on too many factors like size of the system, qualification of your programmers, the existing "ecosystem" of your software, the migration … Hell, it may be true that future changes will be more expensive after the migration, it really depends. …

We want to move to a web-based app so we can eliminate the dependency on our physical location for hiring new sales force members. If that is the main motivation behind your project, please cons …

So as long as you implement the migration in a repeatable, idempotent manner, that should be not much of a problem. … What I cannot tell you is if fiddling around with the time stamps of your migration table will be a problem - for this one needs to know the gory details of your framework. …

You wrote Soon we find that some old project takes long time in running the migration file But why do you have to run the migrations more than once? …

This is ok as long as you are 100% sure the merged migrations will never hit a database which is in an intermediate state (so, for example, the Surname column is there, though it should not). This d …

Think big, start small. The most effective way I know for tackling the described situation is the following approach: Scetch your "vision" of the full data model, but do not implement it with all the …

This is a little bit hard to answer without knowing more about your CMS, but when I got this right, a `pageNode" should be able to store a list of foreign key references to all kind of "referenced thi …

Hardcoded IDs refering to some special records in your database can only work in a reliable way if the creation of those records (including their IDs) is hardcoded in a comparable fashion, ideally wit …

Even an operation like "split a column into two" with some data migration is possible here, as long as the original column is not deleted right now. If this step fails, roll back the DB. …