From the logs, I see:
5eb-f677-4cbc-9eed-60693bb74858] 2022-12-08T10:34:36+00:00 WARN metabase.driver.sql-jdbc.sync.describe-table Don't know how to map column type 'bigint identity' to a Field base_type, falling back to :type/.
[7276a5eb-f677-4cbc-9eed-60693bb74858] 2022-12-08T10:34:36+00:00 WARN metabase.driver.sql-jdbc.sync.describe-table Don't know how to map column type 'bigint identity' to a Field base_type, falling back to :type/.
[7276a5eb-f677-4cbc-9eed-60693bb74858] 2022-12-08T10:34:37+00:00 WARN metabase.sync.util Error checking if Fields ("Date" "RoomId" "BookedPoints" "WeekCommencing" "BookingTypeId" "SessionStart" "SessionTemplateId" "BookingCount" "AppointmentTypeId" "EndoscopistId" "PerformedPoints" "SiteId" "ServiceType" "BookingType") need to be created or reactivated
org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "metabase_field_pkey"
Detail: Key (id)=(8566) already exists.
I assume it's related to the SQL driver problems yesterday.
It worked two days ago! We're rolling back so may not be able to provide much more information.
The columns in the views are defined as bigints. They just reflect what's in the underlying database that hasn't changed. i have no control over that bit.
I'll try casting the identifiers to something smaller.
Edit: This is SQL Server, so no case sensitivity.
2nd Edit: They're not identity columns, just defined as keys in the Data Model.
@AndrewMBaines I think you're mixing different things together. You like have some bigint identity columns, but likely completely unrelated to your problem, and those warnings have likely always been there.
There's case-sensitivity in Postgres, which is your Metabase application database.
Something is causing Metabase to try to re-create metabase_field.id=8566 (whatever that field is).
I'm sure there's other logs.
@AndrewMBaines It sounds like you've lost the auto-increment on your application database, since it should never ever try to insert a conflicting ID. You are having problems with both metabase_table and metabase_field (and likely others too).
Changing any IDs will result in broken questions etc.