Flat File Source Patterns - SQL Server Integration Services Design Patterns - page 189

found in the source file. However, you should also use the strong data types you cre-
ated in our Derived Column transformation. Fortunately for you, our naming conven-
tion makes these changes relatively painless. Simply delete the DDL for the first three
columns ( RecordType , Name , and Value ), and then remove the first three letters of
the remaining columns, which will rename them to RecordType , Name , and Value .
Listing 7-3 shows the result.
Listing 7-3 . The Modified CREATE TABLE Statement
CREATE TABLE [FlatFileDest] (
[RecordType] varchar(1),
[Name] varchar(50),
[Value] int
)
When you click the OK button, the DDL statement is executed against Sta-
gingDB —creating the FlatFileDest table. That's a good thing, because your
OLE DB destination adapter is warning you that you need to complete Input-to-Output
mappings (shown in Figure 7-6 ).
Figure 7-6 . The columns have not been mapped
As shown in Figure 7-7 , when you click on the Mappings page to begin this map-
ping, auto-mapping kicks in and finds it can auto-complete some of the mappings:
Figure 7-7 . OLE DB destination auto-mapping