There are many more situations where you must still reboot and it won't tell you (usually .
It does indicate that there is no added value by going to the "Ready to update" window. This would preferably be a VM that you could snapshot, so if you encounter and fix a problem you can revert to the snapshot and start again with your updated procedure.SQL Server 2000 was a really solid release, and with SP4, it's a really stable database platform.Yes, it's old and support ends next year, but we'll see people using it for many years to come.if your dev/test/release process isn't just "smash code together and throw directly into production"! This way you are essentially treating the service pack the same as you would one of your own bug fix or feature releases meaning you can perform a full regression test on your application after the service pack is applied to the test environment (to make sure MS haven't introduced any bugs or changes to undefined behaviour that your application depends upon - or that they haven't fixed a bug that your code is depending on! Obviously this "ideal" could be more time consuming than other options...Concur, where a separate test system exists from the production, update the test first, then update production.