Copy Database Wizard (Select Database Objects)

  • Article

Use this page to select the objects to include in the move or copy operation. To include an item in the move or copy operation, click the object name in the Available related objects box, and then click the >> button to move the object to the Selected related objects box. To exclude an item in the move or copy operation, click the object name in the Selected related objects box, and then click the << button to move the object to the Available related objects box.

By default, all objects of each selected type, except logins, are transferred. To select individual objects of any type, click the ellipsis button next to any object type in the Selected related objects box. This opens a dialog box where you can select individual objects.

Encrypted objects that include certificates and keys cannot be transferred by the wizard.

Note

This page is only available when the source and destination are different servers. For more information about database objects that are not transferred by the wizard or that require modification after transfer, see Using the Copy Database Wizard.

Options

  • Logins (All logins at run time)
    Include logins in the transfer operation. Selected by default. A login name can be changed on the destination server by changing the value in the Destination Name column.

    Note

    The transfer operation might fail if you select the Copy only the selected logins: option and then clear a login used by a selected database or select a login not used by a selected database that cannot be validated.

    To view the Logins dialog box, click the ellipsis button:

    Details Column

    • Login Exists. Login already exists on the destination server.
    • Sid Exists. The source server login's SID is already used by another login on the destination server.
    • Attach method SID mismatch. Instance account (with “$”s) going cross-instance, Windows local account going cross-machine, or Windows domain account going cross-domain.
    • Type Mismatch. Source and destination logins are different types (SQL, Windows Local, Windows Domain, Cert, AsymKey, HasCredential, Builtin)
    • Insufficient server roles. Existing destination login with less fixed server role permissions than the source login.
    • Certificate. Manual certificate login, creation required at destination.
    • Asymmetric Key. Manual asymmetric key, login creation required at destination.

    Destination Status Column

    • Ok. OK to create the source server login on the destination server.
    • Already Exists. OK to use existing destination server login for a user in a database that is being transferred.
    • Manual. Manual changes to destination are needed before a successful transfer is likely.
    • Error. Error conditions exist that prevent successful transfer until resolved.

  • Stored procedures from master database
    Include user stored procedures from the master database in the move or copy operation.

    Note

    Extended stored procedures and their associated DLLs are not eligible for automated copy in SQL Server 2005.

  • SQL Server Agent jobs
    Include jobs from the msdb database in the move or copy operation.
  • User-defined error messages
    Include user-defined error messages in the move or copy operation.
  • Endpoints
    Include endpoints defined in the source database. SQL Server 2005 only.
  • Full-text catalog
    Include full-text catalogs from the source database. SQL Server 2005 only.

  • SSIS Package
    Include SSIS packages defined in the source database. SQL Server 2005 only.

    After you click the ellipsis button the following applies:

    • For SQL Server 2000 sources, the path column and the Duplicate package folder structure on destination for selected packages option are not shown.