Upgrading Compiled Objects in Database Dumps

When you load a database dump that was created in an earlier version than the current Adaptive Server you are running, you are not required to perform the preupgrade tasks before loading the dump. Learn how to determine whether a compiled object has been upgraded.

You do not receive any notification if the compiled objects in your database dump are missing their source text. After loading a database dump, run sp_checksource to verify the existence of the source text for all compiled objects in the database. Then, you can allow the compiled objects to be upgraded as they are executed, or you can run dbcc upgrade_object to find potential problems and upgrade objects manually.

For information on using sp_checksource, see the Reference Manual: Procedures.

Look at the sysprocedures.version column. If the object was upgraded, this column contains the number 12500.
If you are upgrading to a 64-bit pointer size in the same version, look at the sysprocedures.status column. It contains a hexadecimal bit setting of 0x2 to indicate that the object uses 64-bit pointers. If the bit is not set, the object is a 32-bit object, which means the object has not been upgraded.