December 23, 2005 at 6:27 pm
December 26, 2005 at 8:00 am
This was removed by the editor as SPAM
December 28, 2005 at 12:42 pm
December 28, 2005 at 4:21 pm
Joshua,
I pointed Advisor to SQL 2000 database and it came back with very minor recommendations. Do you think it is better to generate script for all database objects and let Advisor process it?
Thanks,
Igor
December 29, 2005 at 12:32 am
The Upgrade Advisor will catch any code in stored procedures, views, etc. as well as any functional dependencies on deprecated components or changed components. If you also specify trace files or sql scripts, you can analyze code that lives "outside" of the database itself (i.e. analyzing a trace file that was run against the database will help catch embedded T-SQL calls). The analyzer can't analyze extended stored procs
For the databases I've run it in, it has caught all dependencies on system objects, changed features (such as Mail), etc. without issue. I've had a few databases that reported very few problems; it may be the case that your database simply doesn't have that many issues with upgrading to 2005.
Again, I would check the documentation in the Upgrade Advisor. There are quite a few issues to read through, but knowing them and checking your servers/databases against that list will help avoid problems that the Advisor may have missed.
Hope that helps.
December 29, 2005 at 10:09 am
Joshua,
Thanks for your feeback!
Igor
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply