Upgrading compiled objects with dbcc upgrade_object
110 Adaptive Server Enterprise
For example, if you have a user-defined stored procedure named list_proc, the
presence of source text for
list_proc is verified when you upgrade to Adaptive
Server 15.0. The first time
list_proc is invoked after the upgrade, Adaptive
Server detects that the
list_proc compiled object has not been upgraded.
Adaptive Server recompiles
list_proc, based on the source text in syscomments.
The newly compiled object is then executed.
Upgraded objects retain the same object ID and permissions that they used
before being upgraded.
Compiled objects for which the source text was hidden using
sp_hidetext are
upgraded in the same manner as objects for which the source text is not hidden.
For information on
sp_hidetext, see the Reference Manual:Procedures.
Note If you are upgrading from 32-bit installations to use a 64-bit Adaptive
Server, the size of each 64-bit compiled object in the
sysprocedures table in
each database increases by approximately 55 percent when the object is
upgraded. The pre-upgrade process calculates the exact size. Increase your
upgraded database size accordingly.
To ensure that compiled objects have been upgraded successfully before they
are invoked, you can upgrade them manually using the
dbcc upgrade_object
command. For details, see “Finding compiled object errors before production”
on page 110.
Finding compiled object errors before production
Changes made in earlier versions of Adaptive Server may cause compiled
objects to work differently in version 12.5.x and later. You can use
dbcc
upgrade_object
to find the following errors and potential problem areas that
may require manual changes to achieve the correct behavior:
• Reserved word errors
• Missing, truncated, or corrupted source text
• Quoted identifier errors
• Temporary table references
• select * potential problem areas
