v8.1 migration from v7 results in an error due to a unique index on cmsContent
See original GitHub issueWe’ve seen a database migration from v7 to v8.1 fail due to the presence of an index named IX_cmsContent
. This index might be linked to other tables that make it fail.
Need to investigate (this was reported by @marcemarc ).
This item has been added to our backlog AB#2134
Issue Analytics
- State:
- Created 4 years ago
- Comments:24 (17 by maintainers)
Top Results From Across the Web
umbraco 7151 migration to 82 fails
I'm trying to migrate a client's database from v7.15.1 to v8.2 it ... I've tried migration to v8.0 through v8.2.1 with the same...
Read more >v8.1.4
v8.1.4. Status: Released ... 5804 - v8.1 migration from v7 results in an error due to a unique index on cmsContent · 5827...
Read more >Migration exception - could not create unique index
I have a schema for customer is as following: CREATE TABLE dbo.customer ( id uuid NOT NULL, id_number integer NOT NULL, name character ......
Read more >"Migration of 'Vault' failed: The CREATE UNIQUE INDEX ...
"Migration of 'Vault' failed: The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo.
Read more >Unique Indexes — MongoDB Manual
A unique index ensures that the indexed fields do not store duplicate values; i.e. enforces uniqueness for the indexed fields. By default, MongoDB...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The PR is here https://github.com/umbraco/Umbraco-CMS/pull/6121
It’s slightly hard to to test this because if you are using a dacpac you have to manually populate all of the basic data required to run which is a fair few tables. I’ll see if i can post a nightly build to here to see if @robertjf , @rgdagostino or anyone else can test, stay tuned.
@rgdagostino Glad to see some progress! You might have a lot of data to migrate, I ran into a similar issue with a large database, try to fiddle with the timeouts in web.config: https://github.com/umbraco/Umbraco-CMS/issues/5803