We use the same MS SQL database for many applications. I am aware that such action is not recommended however, unfortunately it is the method that will have to be applied.
I work with code first and each time I create an application and try to run a migration on my database, a code is generated that applies drop to the tables of other applications.
Currently in my Package Manager Console I run Update-Database -script and set manually or even apply the same command to a local bank and run the code in my MS SQL database.
Is there a way to work simultaneously with multiple migrations without interfering with another application if the tables have different names?