Parallelize Script Update Mode
When moving SQL Server between Cumulative Updates, Script Update Mode runs against each database on the instance in series. This works fine on smaller instances, but with hundreds or even thousands of databases on an instance, this can add a lot of time (several hours) to the process of starting the instance for the first time with the new CU.
Suggestion: Run Script Update Mode in parallel, up to the MAXDOP setting for the instance.
Sebastian Toet commented
Yes, great idea. We have a SaaS solution, where each customer has a separate database (mainly to enable point-in-time restores for each customer separately), and our instances have up to 5000 databases. This causes 2-3 hours of downtime for a CU installation.
Brett Hollomon commented
We have over 9,000 databases and yes SP's and CU's take a long time. btw, so does development on a workaround to be able to drop a database if each database represents work done for a customer.
Grey Smith commented
This would be great for our system. We currently have 1500 databases on a production system. CU updates take over an hour.