sp_post_xpload

Checks and rebuilds indexes after a cross-platform load database where the endian types are different.

Syntax

sp_post_xpload [force]

force – when specified, uses reindex_opt_force for dbcc reindex in sp_post_xpload.

Example 1 – Once the database is loaded from another platform, rebuilds its indexes by executing:
```
sp_post_xpload
```

The following indexes are rebuilt on all user tables in the database:
- Nonclustered index on an APL table
- Clustered index on a DOL table
- Nonclustered index on a DOL table
Indexes on system tables are not processed with sp_post_xpload only. System table indexes are rebuilt when online database is executed.
You can also rebuild indexes using drop index and create index.
Run sp_post_xload only when the database is loaded across platforms with different endian types.
Where the index status is suspect, reset the index by executing sp_post_xpload, drop index, or create index.
Stored procedures are recompiled from the SQL text in syscomments at the first execution after the load database. Use dbcc upgrade_object to upgrade objects if you do not have permission to recompile from text.

See also dump database, load database in Reference Manual: Commands.

The permission checks for sp_post_xload differ based on your granular permissions settings.

Setting	Description
Enabled	With granular permissions enabled, you must be a user with `load database` privilege or `own database` privilege on the database.
Disabled	With granular permissions disabled, you must be a user with sa_role.

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

Information	Values
Event	38
Audit option	exec_procedure
Command or access audited	Execution of a procedure
Information in `extrainfo`	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