Finding Compiled Object Errors Before Production - Sybase Adaptive Server Enterprise 15.0.2 Installation Manual

Upgrading compiled objects with dbcc upgrade_object

Finding compiled object errors before production

110
For example, if you have a user-defined stored procedure named
presence of source text for
Server 15.0. The first time
Server detects that the
Adaptive Server recompiles
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
upgraded in the same manner as objects for which the source text is not hidden.
For information on
sp_hidetext
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
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
command. For details, see "Finding compiled object errors before production"
on page 110.
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
to find the following errors and potential problem areas that
upgrade_object
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
is verified when you upgrade to Adaptive
list_proc
is invoked after the upgrade, Adaptive
list_proc
compiled object has not been upgraded.
list_proc
, based on the source text in
list_proc
, see the Reference Manual:Procedures.
list_proc
syscomments
sp_hidetext
table in
sysprocedures
dbcc upgrade_object
dbcc
Adaptive Server Enterprise
, the
.
are