We are updating an old production database server to a more current structure. Old is Server 2003 (x86) running SQL 2000 product version 8.00.760. The plan is to update the database to SQL 2008r2 then on to SQL 2012.
Downloaded and installed the SQL Server 2008r2 upgrade advisor on a workstation(Win7 pro 64) with SQL Server 2008r2 sp2 installed. Took a backup of the 2000 database and moved the .bak file to the workstation and restored the bak file, leaving it in the original compatibility mode, DBCC returned no errors.
Ran the Upgrade Advisor against the old server and receive a list of 19 method errors.. all PreUpgrade labeled. (I didn't install UA on the old server as it's still running production jobs and is Seriously under powered.)
Message"Method not found: 'System.Collections.Generic.IEnumerable`1<Microsoft.SqlServer.Management.SqlParser.Parser.Error> Microsoft.SqlServer.Management.SqlParser.SqlCodeDom.SqlCodeObject.get_Errors()'." the methods are:
| DROPSYSOBJ |
| OLDSYSTEMTABLES |
| FTCATALOGNAMERESTRICTION |
| ORDERBYORDINALS |
| VIEWFORBROWSE |
| FTPROPS |
| DUMPLOAD |
| SPHELPTRIGGERNEWCOL |
| MERGE |
| FTCATPROPITEMCOUNT |
| SYSPERFINFO |
| INVALIDCHAR |
| NONANSIOUTER |
| XPAGENTPROXY |
| SPCONFIGURE |
| HOSTIDRETURN |
| DEPRECATEDSP |
| OLDDBCC |
| ORDERBYALIAS |
| DBCCCONCURRENCYVIOLATION |
| INFOSCHEMATA |
| TRACEFLAGS |
| BACKUPRESTORETRANSACTION |
| DBCOMPTLEVEL |
| BACKUPLOG |
| LARGECONSTTYPE |
| VIEWCHECKOPT |
| SYSLOCKINFO |
FORXMLAUTO |
Still haven't found a way to address these, not sure they have to be (??). Came across some posts that seemed to indicate these are generated by running Upgrade Advisor remotely against older targets.
Just for fun ran the upgrade advisor against the backup that was restored onto theWin7 box and received one error which is DEPRECIATEDSP method. I updated the compatability level to 100 ran Upgrade Advisor again with same results, the subsequent DBCC CheckDB would indicate no errors. From what I have been able to find in the forums, it looks like all is well for this part of it (maybe). Are these issues/errors really no longer of concern or are they just ignored(?) masked by the new version of SQL and still in play? ( I don't know if that makes sense it's the best way I can word it at this time)?