| Lesson 10 | SQL Data Integration |
| Objective | Run the SQL Server Import and Export Wizard. |
SQL data integration is the process of moving, consolidating, and transforming data between systems so that decision-makers and applications always work from a single, consistent source of truth. In SQL Server 2022, Microsoft provides a layered toolkit for this work. At the entry level sits the SQL Server Import and Export Wizard, a point-and-click utility built on top of SQL Server Integration Services (SSIS) that handles straightforward data transfers without requiring any code. For production-grade ETL pipelines, SSIS itself provides a full visual development environment inside Visual Studio 2022. This lesson walks through both tools in practical terms.
Background: From DTS to SSIS
Before SQL Server 2005, Microsoft shipped a data-movement tool called
Data Transformation Services (DTS). DTS was useful for its era but was
limited in scalability, error handling, and maintainability. SQL Server 2005
replaced it entirely with SQL Server Integration Services (SSIS), which
introduced a proper package model, a visual data-flow designer, and robust logging.
DTS is not available in any currently supported version of SQL Server. If you
encounter documentation that references DTSWizard.exe or DTS packages,
treat it as a historical artifact. The executable name DTSWizard.exe
was reused for the modern Import and Export Wizard as a legacy shortcut, but the
tool itself runs entirely on the SSIS engine.
The Import and Export Wizard is the fastest path for one-time or occasional data transfers. It supports a wide range of sources and destinations including SQL Server databases, flat files (CSV, TXT), Microsoft Excel, Microsoft Access, Oracle, and any OLE DB or ODBC-compliant data source. The wizard generates an SSIS package behind the scenes and either runs it immediately or saves it for later use. It does not require Visual Studio or any development environment.
Typical use cases include loading a vendor-supplied CSV file into a staging table, exporting a query result to Excel for a business analyst, migrating a table from one SQL Server instance to another, and doing a quick data validation pull between two databases.
Launching the Import and Export WizardThere are four standard ways to open the wizard:
Method 1: SQL Server Management Studio (SSMS)Run DTSWizard.exe directly. The default installation paths are:
64-bit: C:\Program Files\Microsoft SQL Server\160\DTS\Binn\DTSWizard.exe
32-bit: C:\Program Files (x86)\Microsoft SQL Server\160\DTS\Binn\DTSWizard.exe
The folder number 160 corresponds to SQL Server 2022. Earlier versions
use 150 (SQL Server 2019), 140 (2017), and so on.
Azure Data Studio does not ship with the Import and Export Wizard built in, but you can install the SQL Server Import extension from the Extensions Marketplace. This extension provides a flat-file import workflow directly inside Azure Data Studio and is a practical alternative when SSMS is not installed on the workstation.
Walking Through the WizardRegardless of how you launch it, the wizard presents the same sequence of screens:
The wizard covers straightforward transfers well but has real limits. It does not support conditional logic, looping, error redirection to a quarantine table, or incremental loads based on a watermark column. For any of those requirements, you need a full SSIS package developed in Visual Studio 2022.
When data integration requirements grow beyond what the wizard handles, SSIS packages
developed in Visual Studio 2022 with the SQL Server Data Tools (SSDT) extension are
the standard solution. An SSIS package is a saved unit of work stored as a
.dtsx file. It contains a control flow (the sequence of tasks), one or
more data flows (the movement and transformation of rows), connection managers, event
handlers, and variables. The following steps cover the full setup and deployment
sequence for SQL Server 2022.
Note: Analysis Services, Integration Services, and Reporting Services project templates are delivered as separate Visual Studio Marketplace extensions, not as part of the base SSDT workload.
Step 2: Install the SSIS Extension
This extension adds the Integration Services project template and the SSIS Designer
to Visual Studio. Without it, .dtsx files open as raw XML.
Visual Studio creates the project with a default package named
Package.dtsx already open in the SSIS Designer.
Setting the target version before designing the package prevents deployment errors caused by components or features that are not available in an older catalog version.
Step 5: Design the Control Flow and Data FlowAn SSIS package has two design surfaces. The Control Flow tab defines the sequence of tasks and the precedence constraints between them. Common control flow tasks include the Data Flow Task, the Execute SQL Task (for running T-SQL statements), the File System Task (for moving or archiving files), and the Script Task (for C# or VB.NET logic that has no built-in task equivalent).
The Data Flow tab, accessed by double-clicking a Data Flow Task, defines how rows move from source to destination. A typical data flow contains:
SSISDB catalog folder.Note: The SQL Server Agent service must be running to schedule package execution. Verify its status in SSMS under the SQL Server Agent node before creating the job.
Using WITH, JSON, and VECTOR in SSIS Data FlowsSQL Server 2022 added native JSON functions, the REGEXP family of pattern-matching functions, and the VECTOR and VECTOR_DISTANCE functions for AI similarity search. These can be used inside SSIS through the Execute SQL Task and the OLE DB Source component. For example, an OLE DB Source can issue a query using a Common Table Expression (WITH clause) to pre-aggregate data before it enters the data flow, reducing the volume of rows that transformation components must process. A VECTOR_DISTANCE call in a source query can pre-filter rows by semantic similarity before they reach a Conditional Split. JSON_VALUE and JSON_QUERY extract scalar values and sub-objects from JSON columns, making it straightforward to flatten semi-structured data into relational rows inside a Derived Column transformation. These SQL Server 2022 features do not require any change to the SSIS package model itself - they are expressed as T-SQL inside the source query or Execute SQL Task, and SSIS transports the result set as it would any other rowset.