Run the SQL Server Import and Export Wizard

The SQL Server Import and Export Wizard provides the simplest method of copying data between data sources and of constructing basic packages. For more information about the wizard, see SQL Server Import and Export Wizard.

In SQL Server Management Studio, connect to the Database Engine server type, expand Databases, right-click a database, point to Tasks, and then click Import Data or Export data.

—or—

In a command prompt window, run DTSWizard.exe, located in C:\Program Files\Microsoft SQL Server\100\DTS\Binn.

Note

On a 64-bit computer, Integration Services installs the 64-bit version of the SQL Server Import and Export Wizard (DTSWizard.exe). However, some data sources, such as Access or Excel, only have a 32-bit provider available. To work with these data sources, you might have to install and run the 32-bit version of the wizard. To install the 32-bit version of the wizard, select either Client Tools or SQL Server Data Tools (SSDT) during setup.

To import or export data by using the SQL Server Import and Export Wizard

Start the SQL Server Import and Export Wizard.

On the corresponding wizard pages, select a data source and a data destination.

The Microsoft OLE DB Provider for Oracle does not support the Oracle BLOB, CLOB, NCLOB, BFILE, and UROWID data types. Therefore, the OLE DB source cannot extract data from tables that contain columns with these data types.

If the destination is a SQL Server database you can specify the following:

Indicate whether to create a new database and set the database properties. The following properties cannot be configured and the wizard uses the specified default values:

Property

Value

Collation

Latin1_General_CS_AS_KS_WS

Recovery model

Full

Use full-text indexing

True

Select whether to copy data from tables or views, or to copy query results.

If you want to query the source data and copy the results, you can construct a Transact-SQL query. You can enter the Transact-SQL query manually or use a query saved to a file. The wizard includes a browse feature for locating the file, and the wizard automatically opens the file and pastes its content into the wizard page when you select the file.

If the source is an ADO.NET provider you can also use the option to copy query results, providing the DBCommand string as the query.

If the source data is a view, the SQL Server Import and Export Wizard automatically converts the view to a table in the destination.

Indicate whether the destination table is dropped and then re-created, and whether to enable identity inserts.

Indicate whether to delete rows or append rows in an existing destination table. If the table does not exist, the SQL Server Import and Export Wizard automatically creates it.

If the destination is a Flat File destination you can specify the following:

Specify the row delimiter in the destination file.

Specify the column delimiter in the destination file.

(Optional) Select one table and change the mappings between source and destination columns, or change the metadata of destination columns:

Map source columns to different destination columns.

Change the data type in the destination column.

Set the length of columns with character data types.

Set the precision and scale of columns with numeric data types.

Specify whether the column can contain null values.

(Optional) Select multiple tables, and update the metadata and options to apply to those tables:

Select an existing destination schema or provide a new schema to which to assign tables.

Specify whether to enable identity inserts in destination tables.

Specify whether to drop and re-create destination tables.

Specify whether to truncate existing destination tables.

Save and run a package.

If the wizard is started from SQL Server Management Studio or the command prompt, the package can run immediately. You can optionally save the package to the SQL Server msdb database or to the file system. For more information about the msdb database, see Package Management (SSIS Service).

When you save the package you can set the package protection level, and if the protection level uses a password, provide the password. For more information about package protection levels, see Access Control for Sensitive Data in Packages.

If the wizard is started from an Integration Services project in SQL Server Data Tools (SSDT), you cannot run the package from the wizard. Instead, the package is added to the Integration Services project from which you started the wizard. You can then run the package in SQL Server Data Tools (SSDT).

Note

In SQL Server Express, the option to save the package created by the wizard is not available.