I wonder if anyone has had this issue when migration from latest v10 to v12? https://github.com/umbraco/Umbraco-CMS/issues/16311 I have upgraded several sites from v10 to v12 without issues, but this site has a lot of content nodes (mainly a lot of course and category nodes) and timeout during booting and I don't see the maintenance page which migration is running in background. I could upgrade the site locally by increasing Connection Timeout, but I am not sure if we can do that on Umbraco Cloud environments?

How much timeout do you have on your appsettings?

@Bjarne Fyrstenborg I am working on a large multi-site migration and when I take it from v10 to v12 I get timeouts every time but I just run it again when it happens and usually after the third time it completes.

We ended up connection local application with increased connection timeout with connection string pointing development and later live database. Initially we just tried run the migration several times, but each time it was sufficient to complete migration. On most Umbraco projects it probably isn't an issue, but for this specific project, it has a lot of content nodes, which was why the migration took so long.

As well as the sqltimeout, I was also hitting a netcore startupTimeLimit (defaults to 120s max is 3600s) so had to increase via web.config

<aspNetCore startupTimeLimit="3600" processPath=".\Web.exe" arguments="" stdoutLogEnabled="false" stdoutLogFile=".\logs\stdout" hostingModel="InProcess" />

only docs appear to be in netcore 3.1 https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1#configuration-with-webconfig

Interesting, I wonder why since the long running migration process can only begin after the application has started?

This is one of those things that pops up a lot - there's a lot of SQL to chug through on an upgrade. The bigger the site, the more there is to do. The bottleneck is SQL compute - a re-index of all the millions of rows of property data is the most taxing thing the SQL server will ever have to do with an Umbraco site. You can increase the timeout, or increase the compute, or both. This is relatively easy in Azure where we can just up the available compute temporarily. For Cloud, if we know we need to do something intense like this then we just do it locally on a faster machine and then replace the database on Cloud.

How do you replace the database on cloud?

SQL Server Management Studio 😁 Not for the feint of heart.

Didn't really check, but they have about 40K nodes in external index. Probably some unpushled + some trasched. I have seen projects with hundreds of nodes in recycle bin, so it would of course help at bit emptying the recycle bin as well.

Or Azure data studio + sql server DacPac extension (included in Admin Pack for SQL Server)... though with cloud not sure what the process would be.. as not sure you can replace with a bacpac... wouldn't you have to create a new one and then alter the connection string? Wouldn't have thought cloud allowed you to create a second/new db?

There's a beta version to Backup Umbraco Cloud databases, but currently when I have tested this it was 3 x slower than directly using export data tier application from SSMS. It is also only possible to have 1 database per environment, but I suggested some time ago it would be great to create more databases, e.g. to move create Hangfire, Ucommerce, Umbraco Commerce etc. db tables or custom data in separata database as we had a client requested it, but it would be great one didn't need a separate account on Azure or elsewhere to have an additional database. The backup tool in the portal also have an restore option (for created databases), but seems to be disabled for now .. perhaps in future it is possible to upload bacpac file and restore to an Umbraco Cloud database?

I said it wasn't for the feint of heart...

Yes, one of the first steps in my migration process is to empty both content and media recycle bins so we are not processing nodes unnecessarily.

HQ are internally testing an "import db" feature. So hopefully some day we'll be able to 🙂