Check out the upgrade-advisor !

http://www.microsoft.com/downloads/details.aspx?FamilyID=6107C27A-662C-4319-AFE7-B52D1568C30A&displaylang=en

It will check your current db, .. and highlite some issues (if found )

the BINARY_CHECKSUM and checksum solution is great, but know their downsides (text/image/...)

It's all in Bol

So for the sqlserver-instance it's an existing db which will be detatched and reattatched, only having the files at a diffent location.

In that case, the sync is not needed.

What the...

yep.

don't forget users and passwords and their synchronisation

it depends

If you want to create the possibility for you users that they access you sqlserver using only your application, or also...

The mentioned URL should contain this :

-- The goal is to avoid the use of sp_start_job in an application. So we have the application use RAISERROR to activate the job.

-- ...

you may also want to run sp_updatestats ! (if you are alowed to)

Did you rebuild your clustering index ?

yep. Keep it simple.

If you have DRI (foreign keys), you may want to hold them until after the load !

Or you will have the burdon of a loadsequence exercise.

Test it,...

can you post your table and index DDL ?

Since the old server is the onlyone having SQL_Latin1_General_CP1_CI_AS , and the others use Latin1_general_CI_AS , maybe this is _the_ occasion to migrate !

This way, when all servers...

at collation level : yes.

We have a mix of 7.0 and sql2000 and are implementing sql2005, still using SQL_Latin1_General_CP1_CI_AS because of the # of servers and databases that have to...

Maybe this helps to figure it out ...

Keep in mind it uses systemtables, which is no a best practise

-- Select  'DBCC UPDATEUSAGE  ('''...

When you use "restore db" to put your db on SQL2005, then it will still have and use it's own collation. That could already be done in SQL2000.