Chapter 1: System Procedures

sp_remap

Description

Remaps a stored procedure, trigger, rule, default, or view from releases later than 4.8 and prior to 10.0 to be compatible with releases 10.0 and later. Use sp_remap on pre-existing objects that the upgrade procedure failed to remap.

Syntax

sp_remap objname

Parameters

objname: is the name of a stored procedure, trigger, rule, default, or view in the current database.

Examples

Example 1

Remaps a stored procedure called myproc:

sp_remap myproc

Example 2

Remaps a rule called default_date. Execute a use my_db statement to open the my_db database before running this procedure:

sp_remap "my_db..default_date"

Usage

If sp_remap fails to remap an object, drop the object from the database and re-create it. Before running sp_remap on an object, it is a good idea to copy its definition into an operating system file with the defncopy utility. See the Utility Guide for more information about defncopy.
sp_remap can cause your transaction log to fill rapidly. Before running sp_remap, use the dump transaction command to dump the transaction log, as needed.
You can use sp_remap only on objects in the current database.
sp_remap makes no changes to objects that were successfully upgraded to the current release.

Permissions

Only a System Administrator or the owner of an object can execute sp_remap.

Auditing

Values in event and extrainfo columns from the sysaudits table are:

Event	Audit option	Command or access audited	Information in extrainfo
38	exec_procedure	Execution of a procedure	Roles – Current active roles Keywords or options – NULL Previous value – NULL Current value – NULL Other information – All input parameters Proxy information – Original login name, if set proxy in effect