SQL Server 2008 Upgrade Advisor

Microsoft introduced the Upgrade Advisor (Upgrade Advisor) in SQL Server 2005. This tool can debug and analyze your current SQL Server database in a secure environment before executing the SQL Server database upgrade plan. The key to success in any project plan implementation is risk management, which can be evaluated without any risk being introduced, and then evaluated one by one to identify possible impediments to escalation, thereby starting the upgrade plan in a manageable manner. The good news is that Microsoft will continue to provide this tool in SQL Server 2008. The object we're going to talk about here is this tool in the new version.

One reason this architecture is popular is that we can install Upgrade Advisor on a separate desktop and then connect it remotely to the original SQL Server machine. The Upgrade Advisor then analyzes debugging in read-only mode and does not change anything on the original server. This will make people feel more comfortable, because SQL Server can continue to operate normally in the debugging analysis process, while we can view the generated analysis results report and start planning upgrades. The Upgrade Advisor lists the identified issues, such as errors or warnings, and so on. For each issue, there is a link to a help document that will tell you more about the problem and the solution. Once you've dealt with these obstacles one after the other, you can mark these issues as resolved. When you run your Upgrade Advisor the next time, the problem that you have resolved will not appear, and you will have to solve the new problems as soon as you have the results report from the Upgrade Advisor. But Microsoft played a little bit of a trick in SQL Server 2005. Even if your server does not find any problems with the analysis test, the Upgrade Advisor will also list at least one database engine error, marked "Other database engine upgrade issues." Microsoft's intention is to get everyone to be vigilant during the upgrade process and not to be complacent, so write this code dead in the program, forcing us to consult the basic documentation of the relevant general escalation issues. We can mark this error as resolved ourselves. Thankfully, Microsoft has adopted this strategy in SQL Server 2008.

In SQL Server 2005, the content of the Knowledge Base (knowledge Base) that provides support for Upgrade Advisor is rich and detailed and useful. Each document provides a detailed explanation of the problem and lists the possible ways and steps to solve the problem. You may be disappointed if you expect the 2008 version to inherit the good traditions of your predecessors. For many of the answers to the questions, the 2008 version of the Knowledge Base is an understatement, with no more useful information. For example, for some SQL Server 2005 features that are no longer supported in SQL Server 2008, the Knowledge base is simply a saying that the feature is no longer supported in this release, and that the way to correct the problem is simply to avoid using the feature in new development work, and so on, And no longer explain the reasons for us in detail. In many people's eyes, SQL Server's Help system "Books Online" may be the best collection of help documents available, but it does not seem to apply to SQL Server 2008, and the Upgrade Advisor Knowledge Base of SQL Server 2008 does not meet this high standard. This may not be related to the lack of a sufficient iteration in the Microsoft test plan, and if there were another candidate, there would be plenty of time to deal with this sort of thing.