SnowConvert AI - SSIS¶
This section provides a comprehensive reference of SSIS elements and components that SnowConvert can convert to dbt and Snowflake. Control Flow elements (tasks and containers) become orchestration logic, while Data Flow components (sources, transformations, destinations) become dbt models.
Control Flow Elements¶
These SSIS Control Flow tasks and containers are supported:
Element |
Category |
Conversion Target |
Notes |
|---|---|---|---|
Microsoft.Pipeline (Data Flow Task) (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/data-flow?view=sql-server-ver17) |
Task |
Complete dbt Project |
- |
Microsoft.ExecuteSQLTask (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/execute-sql-task?view=sql-server-ver17) |
Task |
Inline SQL or Stored Procedure |
- |
Microsoft.ExecutePackageTask (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/execute-package-task?view=sql-server-ver17) |
Task |
Inline EXECUTE TASK or PROCEDURE call |
- |
Microsoft.SendMailTask (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/send-mail-task?view=sql-server-ver17) |
Task |
SYSTEM$SEND_EMAIL with Notification Integration |
Some features not supported; See Send Mail Task section |
Microsoft.BulkInsertTask (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/bulk-insert-task?view=sql-server-ver17) |
Task |
COPY INTO with inline FILE_FORMAT |
Requires stage setup; See Bulk Insert Task section |
STOCK:SEQUENCE (Sequence Container) (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/sequence-container?view=sql-server-ver17) |
Container |
Inline sequential execution |
- |
STOCK:FORLOOP (For Loop Container) (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/for-loop-container?view=sql-server-ver17) |
Container |
Sequential execution |
Manual iteration logic required; Check EWI SSC-EWI-SSIS0004 for more information |
STOCK:FOREACHLOOP (ForEach Loop Container) (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/foreach-loop-container?view=sql-server-ver17) |
Container |
LIST/CURSOR pattern |
Requires stage mapping; Check EWI SSC-EWI-SSIS0014 for more information |
Event Handlers (https://learn.microsoft.com/en-us/sql/integration-services/integration-services-ssis-event-handlers?view=sql-server-ver17) |
Container |
Not converted |
Implement manually using Snowflake exception handling |
Note: Unlisted Control Flow elements generate EWI SSC-EWI-SSIS0004.
Container Conversion Details¶
SSIS containers (Sequence, For Loop, ForEach, Event Handlers) are converted using an inline approach where container logic is expanded within the parent TASK or procedure rather than creating separate procedures.
Sequence Containers¶
Sequence containers (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/sequence-container?view=sql-server-ver17) are converted inline within the parent TASK. The container’s boundaries are marked with comments in the generated code, and all tasks within the container execute sequentially in the same TASK scope.
Conversion characteristics:
No separate procedure or TASK is created for the container
Container boundaries are clearly marked BEGIN … END blocks
All tasks execute sequentially within the parent TASK
Task execution order based on precedence constraints is maintained
Limitation: Only “Success” precedence constraints are fully supported. Conditional execution based on task outcomes (Failure or Completion constraints) is not currently implemented and will require manual post-migration adjustments
Behavioral differences:
FDM generated: SSC-FDM-SSIS0003
Variable scoping differs from SSIS: Container variables are accessible throughout the entire parent TASK, not just within the container scope
Example:
For Loop Containers¶
For Loop containers (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/for-loop-container?view=sql-server-ver17) are converted to sequential execution of their contained tasks. However, the loop iteration logic itself requires manual implementation.
Conversion limitations:
The container executes once by default (iteration logic not automatically converted)
InitExpression, EvalExpression, and AssignExpression require manual conversion
An EWI (SSC-EWI-SSIS0004) is generated to indicate manual work is needed
Required manual steps:
Review EvalExpression to understand the loop termination condition
Implement the iteration using Snowflake’s WHILE loop construct
Update AssignExpression logic for proper loop counter management
ForEach Loop Containers¶
File Enumerator (Supported)
ForEach File Enumerator containers (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/foreach-loop-container?view=sql-server-ver17) are converted to Snowflake stage operations using the LIST command and cursor pattern:
Configuration requirements:
After migration, you’ll need to:
Replace
<STAGE_PLACEHOLDER>with your actual Snowflake stage nameEnsure the folder path is correctly mapped to a Snowflake stage
Verify that files are properly staged in Snowflake
An EWI (SSC-EWI-SSIS0014) is generated to remind you of this manual configuration step.
Other Enumerator Types
Other ForEach enumerator types (ForEach Item, ForEach ADO, ForEach NodeList, etc.) aren’t currently supported. SnowConvert generates an EWI (SSC-EWI-SSIS0004) for these cases. Consider implementing the equivalent logic using Snowflake queries or scripting constructs.
Event Handlers¶
Event handlers (https://learn.microsoft.com/en-us/sql/integration-services/integration-services-ssis-event-handlers?view=sql-server-ver17) (OnError, OnWarning, OnPreExecute, OnPostExecute, etc.) aren’t supported. EWIs are generated. Implement manually using Snowflake exception handling.
Execute SQL Task¶
Execute SQL Tasks (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/execute-sql-task?view=sql-server-ver17) are converted as inline SQL statements or separate stored procedures, depending on complexity and result set bindings.
Conversion approach:
Simple SQL statements: Converted inline within the parent TASK
Complex statements with result sets: May be converted to separate stored procedures
Result bindings: Handled where possible; unsupported patterns generate EWI SSC-EWI-SSIS0011
Execute Package Task¶
Execute Package Tasks (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/execute-package-task?view=sql-server-ver17) are handled differently based on package type:
Package Type |
Conversion |
Notes |
|---|---|---|
Local (single reference) |
Inline execution within parent TASK |
Package logic expanded inline |
Reusable (2+ references or parameters) |
CALL to stored procedure |
Enables synchronous execution with parameters; generates FDM SSC-FDM-SSIS0005 |
External |
CALL with path resolution |
Generates EWI SSC-EWI-SSIS0008 for manual verification |
Asynchronous execution note:
TASK-based Execute Package conversions run asynchronously. For synchronous behavior, packages are converted to stored procedures. See EWI SSC-EWI-SSIS0005.
Send Mail Task¶
Send Mail Tasks (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/send-mail-task?view=sql-server-ver17) are converted to Snowflake Tasks that use SYSTEM$SEND_EMAIL with a dynamically created Notification Integration.
Key Differences from SSIS¶
Aspect |
SSIS |
Snowflake |
|---|---|---|
Email Service |
Custom SMTP server |
Snowflake’s built-in email service |
Configuration |
SMTP Connection Manager |
Notification Integration |
Sender Address |
Custom FROM address |
Fixed by Snowflake account |
CC/BCC Support |
Full support |
Not supported (merged into recipients) |
Attachments |
File attachments supported |
Not supported |
HTML Body |
Supported |
Plain text only |
Priority |
High/Normal/Low |
Not supported |
Property Mapping¶
SSIS Property |
Snowflake Equivalent |
Notes |
|---|---|---|
ToLine |
|
Direct mapping |
FromLine |
Prepended to message body |
|
CCLine |
Added to recipients list |
|
BCCLine |
Added to recipients list |
FDM SSC-FDM-SSIS0010 (privacy concern) |
Subject |
|
Direct mapping |
MessageSource |
|
Direct mapping |
MessageSourceType (DirectInput) |
Supported |
- |
MessageSourceType (Variable) |
Supported |
Variable reference converted |
MessageSourceType (FileConnection) |
Not supported |
|
Priority |
Not supported |
|
FileAttachments |
Not supported |
|
SMTPConnection |
Managed by Snowflake |
|
BodyFormat (HTML) |
Not supported |
Conversion Output Structure¶
Each Send Mail Task is converted to a Snowflake Task containing:
Notification Integration Creation: Created dynamically via
EXECUTE IMMEDIATESYSTEM$SEND_EMAIL Call: Sends the email through the integration
Conversion Examples¶
Basic Email (To, Subject, Body):
Email with FROM Address:
Email with Multiple Features (attachments, priority, CC):
Prerequisites for Snowflake Email¶
Before using converted Send Mail Tasks:
Email Notification Integration permissions: Account admin must grant
CREATE INTEGRATION ON ACCOUNTto the executing roleRecipient verification: All email addresses in
ALLOWED_RECIPIENTSmust be verified in SnowflakeUpdate warehouse name: Replace
DUMMY_WAREHOUSEwith your actual warehouse name
Workarounds for Unsupported Features¶
File Attachments:
Upload files to a Snowflake stage and share links instead:
BCC Privacy:
Send separate emails to maintain recipient privacy:
Bulk Insert Task¶
Bulk Insert Tasks (https://learn.microsoft.com/en-us/sql/integration-services/control-flow/bulk-insert-task?view=sql-server-ver17) are converted to Snowflake Tasks that use COPY INTO with an inline FILE_FORMAT. The conversion generates a stage placeholder that you must configure before execution.
Key Differences from SSIS¶
Aspect |
SSIS |
Snowflake |
|---|---|---|
Data Source |
File system path or UNC path |
Snowflake Stage (internal or external) |
File Format |
Format file (.fmt/.xml) or inline options |
FILE_FORMAT object or inline options |
Native Format |
Native/WideNative supported |
Not supported (CSV, JSON, Parquet, etc.) |
Row Filtering |
FirstRow/LastRow options |
Not directly supported |
Batch Control |
BatchSize configurable |
Automatic management |
Error Handling |
MaximumErrors count |
ON_ERROR behavior |
Triggers |
FireTriggers option |
Not supported (use Streams/Tasks) |
Table Locking |
TableLock option |
Not needed (MVCC) |
Property Mapping¶
SSIS Property |
Snowflake Equivalent |
Notes |
|---|---|---|
DestinationTableName |
|
Square brackets |
DataFileType (Char) |
|
Direct mapping |
DataFileType (Native) |
Not supported |
|
FieldTerminator |
|
Parsed from SSIS format |
RowTerminator |
|
Parsed from SSIS format |
FirstRow |
|
Value - 1 |
LastRow |
Not supported |
|
MaximumErrors |
|
|
KeepNulls=True |
|
Empty tuple |
KeepNulls=False |
|
Default behavior |
KeepIdentity=False |
FDM generated |
|
TableLock=True |
Not needed |
|
FireTriggers=True |
Not supported |
|
FormatFile |
Not supported |
|
CheckConstraints=True |
Always enforced |
|
BatchSize |
Automatic |
|
SortedData |
Not available |
Terminator Parsing¶
SSIS uses specific tokens for field and row terminators. These are converted to Snowflake escape sequences:
SSIS Format |
Snowflake Output |
|---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Conversion Output Structure¶
Each Bulk Insert Task is converted to a Snowflake Task containing a COPY INTO statement with an inline FILE_FORMAT:
Conversion Examples¶
Basic Bulk Insert (CSV with default options):
Bulk Insert with Tab Delimiter and Header Skip:
Bulk Insert with Multiple EWIs (Native format, LastRow, FireTriggers):
Stage Setup (Required)¶
Before executing converted Bulk Insert Tasks, you must:
Create a Snowflake stage:
Upload files using SnowSQL CLI:
Replace the stage placeholder in generated code:
Verify files are staged:
Workarounds for Unsupported Features¶
Native Data Format:
Export SQL Server data to CSV format before migration. The native binary format is not supported by Snowflake.
LastRow Filtering:
Load to staging table and filter:
FireTriggers (Trigger-like Behavior):
Use Snowflake Streams and Tasks:
dbt Project Execution¶
Within the orchestration code, Data Flow Tasks are executed using Snowflake’s EXECUTE DBT PROJECT command:
Important requirements:
The
project_namemust match the name you used when deploying the dbt project (viaCREATE DBT PROJECTor Snowflake Workspace deployment)Arguments passed are standard dbt CLI arguments (like
build,run,test)Each execution runs the entire dbt project with all models in dependency order
Deployment:
Before executing dbt projects in orchestration, deploy them using:
Snowflake CLI:
snow dbt deploy --schema schema_name --database database_name --force package_nameSnowflake Workspace: Upload and deploy via UI
For complete deployment instructions, see the user guide.
Data Flow Components¶
These SSIS Data Flow sources, transformations, and destinations are supported:
Component |
Category |
dbt Mapping |
Model Naming |
Notes |
|---|---|---|---|---|
Source Components |
||||
Microsoft.OLEDBSource (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/ole-db-source?view=sql-server-ver17) |
Source |
Staging Model |
|
- |
Microsoft.FlatFileSource (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/flat-file-source?view=sql-server-ver17) |
Source |
Staging Model |
|
- |
Transformation Components |
||||
Microsoft.DerivedColumn (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/derived-column-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (SELECT with expressions) |
|
- |
Microsoft.DataConvert (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/data-conversion-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (CAST expressions) |
|
- |
Microsoft.Lookup (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/lookup-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (LEFT JOIN) |
|
Might present functional differences for ORDER BY requirements. Check FDM SSC-FDM-SSIS0001 for more information |
Microsoft.UnionAll (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/union-all-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (UNION ALL) |
|
- |
Microsoft.Merge (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/merge-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (UNION ALL) |
|
Might present functional differences for sorted output. Check FDM SSC-FDM-SSIS0002 for more information |
Microsoft.MergeJoin (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/merge-join-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (JOIN) |
|
Might present functional differences for ORDER BY requirements. Check FDM SSC-FDM-SSIS0004 for more information |
Microsoft.ConditionalSplit (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/conditional-split-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (Router pattern with CTEs) |
|
- |
Microsoft.Multicast (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/multicast-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model (SELECT pass-through) |
|
- |
Microsoft.RowCount (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/transformations/row-count-transformation?view=sql-server-ver17) |
Transformation |
Intermediate Model with macro |
|
Uses m_update_row_count_variable macro |
Destination Components |
||||
Microsoft.OLEDBDestination (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/ole-db-destination?view=sql-server-ver17) |
Destination |
Mart Model (table) |
|
- |
Microsoft.FlatFileDestination (https://learn.microsoft.com/en-us/sql/integration-services/data-flow/flat-file-destination?view=sql-server-ver17) |
Destination |
Mart Model (table) |
|
- |
Note: Unlisted Data Flow components generate EWI SSC-EWI-SSIS0001.