Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrating multitenant dbs #6011

Closed
lnaie opened this issue Jul 7, 2016 · 2 comments
Closed

Migrating multitenant dbs #6011

lnaie opened this issue Jul 7, 2016 · 2 comments
Labels
closed-no-further-action The issue is closed and no further action is planned.

Comments

@lnaie
Copy link

lnaie commented Jul 7, 2016

I have to apologize but this topic is not clear as it should be.
Let me explain a bit the context first: I have a design time database where I do all the nifty staff with CF Migrations. That works! Then I need some tool at deployment time, like FluentMigrator, to be able to apply latest db schema changes to all other customer databases. As a side note, apparently 'dotnet ef' command needs the project.json, therefore I wasn't able to use it outside of the Visual Studio project folder. I wanted to build the diff sql script and apply it to all other customer dbs.

Question is how am I supposed to handle this?

@rowanmiller
Copy link
Contributor

We do have plans for a command line executable like dotnet ef that can be used on any compiled assemblies (tracked by #646). In the meantime you can use Script-Migration -Idempotent or dotnet ef migrations script --idempotnent to create a script that can be executed to upgrade a database. Passing the idempotent argument will create a script with the inbuilt logic to check the migrations history table and only apply pending operations.

@rowanmiller
Copy link
Contributor

Closing as I think I've answered the question, but feel free to reply if not.

@rowanmiller rowanmiller added the closed-no-further-action The issue is closed and no further action is planned. label Jul 15, 2016
@ajcvickers ajcvickers reopened this Oct 16, 2022
@ajcvickers ajcvickers closed this as not planned Won't fix, can't repro, duplicate, stale Oct 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-no-further-action The issue is closed and no further action is planned.
Projects
None yet
Development

No branches or pull requests

3 participants