❔ EF CORE 6 Issue: SYSTEM_TIME period is already defined on table
I am converting an existing set of temporal tables to use the EF Core 6 native support for temporal tables. I am using a Code First approach. When I Add-Migration, I get a migration looking like this (migration shown in picture):
When I run Update-Database I get this error: SYSTEM_TIME period is already defined on table 'dbo.User'. From looking for an answer, I see several SQL answers that use IF EXISTS to wrap ALTER statements. Is there a way to
do this using a Code First approach in .Net Core 6?
3 Replies
Looks like nothing has happened here. I will mark this as stale and this post will be archived until there is new activity.
I figured out the answer to this issue (posted it on my stack overflow question for it): https://stackoverflow.com/questions/76725355/ef-core-6-issue-system-time-period-is-already-defined-on-table/76733754#76733754
Stack Overflow
EF Core 6 Issue: SYSTEM_TIME period is already defined on table
I am converting an existing set of SQL Server temporal tables to use the EF Core 6 native support for temporal tables. I am using a code-first approach. When I run Add-Migration, I get a migration
Was this issue resolved? If so, run
/close - otherwise I will mark this as stale and this post will be archived until there is new activity.