Description
openedon May 2, 2020
I note the migration scripts do not contain any information on creating a DB. Which is unfortunate as it seems the settings required for it to work are not defined anywhere, and doing it manually (naively) myself caused errors to be thrown by the generated DB script that were not present when I create the DB using .Migrate() in code. (eg creating a spatial index failed, "the following SET options have incorrect settings 'Quoted Identitfier').
So can the SQL Scripts section be updated to include:
DB creation sql script that works for EF databases (even if only for SQL server)
Currently I'm trying to create a production DB that doesn't require running the app with a connection string that is the SA user. And it just doesn't work out of the box, and isn't as easy as it should be. The dotnet ef tooling seems to be entirely geared towards development, not production use.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.
- ID: 6e28b0a8-b7e4-4c07-9e60-0df403bbee28
- Version Independent ID: 12300b31-6f7b-b75c-970d-693365e77013
- Content: Migrations - EF Core
- Content Source: entity-framework/core/managing-schemas/migrations/index.md
- Product: entity-framework
- Technology: entity-framework-core
- GitHub Login: @bricelam
- Microsoft Alias: bricelam