Upgrade Advisor SQL 2008 and database move to new server

We are currently in the process of upgrading several databases from SQL 2000 and SQL 2005 to SQL Server 2008. We are purchasing new servers and they will be running an active/passive cluster - Windows Server 2008 R2 and SQL Server 2008.
We are going to backup the databases from the old servers and restore to the cluster. We ran the upgrade advisor on each server and have received a multitude of errors.
I believe some of these can be disregarded because we are technically not upgrading the inplace instance of SQL, but moving the databases to SQL 2008. Below are the alerts that I hope to ignore. Can I disregard or do I need to address? Many thanks in advance!

Full-Text Search has changed in SQL Server 2008. Upgrade Advisor detected that full-text search is going to be upgraded. Many full-text search options and settings have changed. Therefore, when you upgrade to SQL Server 2008 Full-Text Search, some of your settings might need modification.
To upgrade and run the Microsoft Full-Text Engine for SQL Server 2008 you must enter an account name and password that is associated with a specific security group, a security feature that is new to SQL Server
Upgrading will cause Full-Text Search to use instance-level, not global, word breakers and filters by default. SQL Server provides a way to allow instance-level registration of new word breakers and filters.
Full-Text Search has changed in SQL Server 2008. Upgrade Advisor determined that Full-text search is currently installed.
Upgrading will cause Full-Text Search to use instance-level, not global, word breakers and filters by default
Database maintenance plans
superseded
SQL Server 2000 DTS Designer components are required to edit DTS packages

asked Mar 06 '10 at 03:54 PM in Default

Z28
1 ● 1 ● 1 ● 1

(comments are locked)

3 answers:

When you upgrade FTi in SQL you should get and upgrade page to allow you run the setup.

I would refer to the msdn link below and review it so that you can be happy with the changes in your environment

MSDN FTi uprade options

answered Mar 06 '10 at 04:08 PM

sp_lock
8.1k ● 20 ● 26 ● 29

(comments are locked)

If you have the time run the restore and test all processes against it before you go live, especially those mentioned in your list. If you can work through the resolution of issues on h/w that is not in production yet then you get to see how the upgrade for real will be best handled.

answered Mar 06 '10 at 07:04 PM

Fatherjack ♦♦
38.8k ● 55 ● 69 ● 104

(comments are locked)

-- It shows you have Full Text Indexing installed. If you are not actually using any Full Text Indexes, you can safely ignore the related warnings. If you are using any Full Text Indexes, you will need to address the related warnings.

Even though you are doing a clean install rather than an in-place upgrade, the settings and behaviors to which the Full Text Index warnings refer will still be different than the settings and behaviors you are currently using. The only way to be sure your Full Text Indexes still operate as expected is to test them after the migration. Find somewhere you can run the migration and test before going live in production.

-- It's a similar situation with the DTS designer components. Are you going to have SQL Server 2000 DTS packages on your SQL Server 2008 instance? If so, you will need the designer components installed on the SQL Server 2008 server if you want the capability to edit the packages from the server itself. If not, you can disregard the warning.

-- You will need to recreate any maintenance plans from scratch. You cannot migrate them to the new platform.

answered Mar 07 '10 at 12:34 AM