Data-Type Conflicts

The runtime error I find most common and frustrating to deal with are data-type conflicts when running SSIS packages. I make it a practice to establish a compatible data type to the destination(s) early in the pipeline. If I’m reading data from a database source such as SQL Server, I can often establish a matching destination data type in the extract query by using the CAST command. If doing so isn’t feasible, you can use the Show Advanced Editor menu option by right-clicking the Data Flow component, which will let you edit the object’s properties. After opening the advanced editor, click the Input and Output Properties tab, expand the OLE DB Source Output level in the tree hierarchy, then expand Output Columns. Click the name of the output column of interest and note or modify the data type and length.