Do Not Keep NULLS using SSIS Bulk Insert - Insert Empty String Ins
- From: Ulysses <Ulysses@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 13 May 2008 13:51:00 -0700
I have two SSIS packages that import from the same flat file into the same
SQL 2005 table. Both packages use the same Connection Managers. The SQL
table allows NULL values for all fields. The flat file has "empty values"
for certain columns.
The first package uses the Data Flow Task with the "Keep nulls" property of
the OLE DB Destination Editor unchecked. When this task is executed no null
values are inserted into the SQL table for the "empty values" from the flat
file. Empty string values are inserted instead of NULL.
The second package uses the Bulk Insert Task with the "KeepNulls" property
for the task set to "False". When the task is executed NULL values are
inserted into the SQL table for the "empty values" from the flat file.
I want to have the exact same behavior on my data in the Bulk Insert Task as
I do with the Data Flow Task. Using the Bulk Insert Task, what must I do to
have the Empty String values inserted into the SQL table where there is an
"empty value" in the flat file? Why & how does this occur automatically in
the Data Flow Task?
.
- Prev by Date: DTS Wizard fails to create truncate statements
- Next by Date: SSIS - Variable String!
- Previous by thread: DTS Wizard fails to create truncate statements
- Next by thread: SSIS - Variable String!
- Index(es):
Relevant Pages
|
