zam6ak wrote:
sorry for the late reply. In our implementation we have one __MigrationHistory per schema as you can see in my sample postet on 19.10.2013:
Regards from Germany,
Tobias
Additional question: How to handle "__MigrationHistory" table?Hi zam6ak,
Should each schema have its own migration history?
sorry for the late reply. In our implementation we have one __MigrationHistory per schema as you can see in my sample postet on 19.10.2013:
tenantDataMigrationsConfiguration.SetHistoryContextFactory("System.Data.SqlClient", (existingConnection, defaultSchema) => new HistoryContext(existingConnection, schemaName));
'schemaName' is the ID (a GUID) of the tenant in our case.Regards from Germany,
Tobias