Checks and rebuilds indexes after a cross-platform load database where the endian types are different.
sp_post_xpload
Once database is loaded from another platform, rebuild 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_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.
Handling suspect partitions in cross-platform dump and load operations
During the first online database command, after you execute load database across two platforms with different endian types, the hash partition is marked suspect.
Any global clustered index on a round-robin partition, which has an internally generated partition condition with a unichar or univarchar partition key, is marked suspect.
After the database is online, use sp_post_xpload to fix the suspect partitions and indexes.
Can only be executed by the System Administrator.
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 |
|
dump database, load database
