Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Lets you change the database name and specify the ___location and names of the database files. This page appears one time for each database being moved or copied.
Note
If a selected database exists on the destination server, the names of the proposed destination database and files are the source name with _new, _new1, and so on appended.
Options
- Source database
Displays the name of the database being moved or copied. This box is read-only.
- Destination database
Accept or change the proposed name of the database that is being transferred.
- Filename
Accept or change the proposed names of the files. The names of full-text catalogs being transferred by using the detach-and-attach method will not appear.
- Size (MB)
Displays the size of the file in megabytes.
- Destination folder
Specify the proposed destination ___location.
- Status
Displays OK if the file can be created, or provides a reason if the file cannot be created.
- Refresh
Refresh the list of databases and files.
- Stop the transfer if a database or file with the same name exists at the destination.
Cancel the copy or move operation if a database that has the same name exists on the destination server.
- Drop any database on the destination server with the same name, then continue with the database transfer, overwriting existing database files.
If a database that has the same name exists on the destination server, the destination database is dropped, and then the copy or move operation continues.
Next
When you click Next, the wizard checks whether the following validations occur:- Database already exists on the destination server.
- Database name is more than 128 characters.
- Database name is empty.
- Another database that is being transferred has the same name.
- File name is empty.
- File path is empty.
- There is insufficient space on the destination server.
- File already exists on the destination server, and the user did not select the option to drop an existing database that has the same name.
- Drive on the destination server is not valid.
- There are insufficient permissions to calculate disk space. This is probably because the user is not a member of the sysadmin fixed server role.
- Another database that is being transferred has the same file name.