3.6.0 Migration Utility for SQL Server Operations Guide (5697-7090, December 2007)

Using MxMigrate 17
Copyright © 1999-2007 PolyServe, Inc. All rights reserved.
NOTE: The user running MxMigrate and the user account under which
the SQL Server process is running must have read, write, list,
create, and delete permission within the folder. This applies to
both the source and target server.
Remove backup files. Check this item if you want to remove the backup
files after a successful restore.
Validation Window
The Validation window allows you to validate the Source and Target
servers before proceeding with the actual database migration.
NOTE: The Validation step verifies only that the database exists; it does
not check the status of the database. If the database is not online
and accessible, the create/backup/restore operations will fail.
Access Check
To check for access to the backup directory, MxMigrate executes the
following from the source and target server:
Exec master..xp_cmdshell N'dir <backup_path or restore_path>
This step requires that xp_cmdshell execution be allowed during the
migration. To turn on xp_cmdshell on SQL 2005, use the SQL Surface
Area Configuration tool or run the following script.
--enable xp_cmdshell for sql2k5
exec sp_configure 'show advance','1'
reconfigure with override
go
exec sp_configure 'xp_cmdshell','1'
reconfigure with override
go
To turn off xp_cmdshell on SQL 2005, use the SQL Surface Area
Configuration tool or run this script.
--disable xp_cmdshell for sql2k5
exec sp_configure 'xp_cmdshell','0'
reconfigure with override
go