• [March 28, 2008]
  • Data-Type Conflicts
  • By:  Erin Welker
  • Features
  • InstantDoc #98171
  • Web Exclusive from SQL Server Magazine
Main Article    Debugging and Logging in SSIS

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.

End of Article


You must log on before posting a comment.

If you don't have a username & password, please register now.

Reader Comments

It's more useful if you can show us how to do it in each step by step instead of saying "Checkpoint aren't enabled by default" or how people how to turn on the switch and test the elements you just mentioned.

LamNguyen- April 25, 2008

Article Rating 1 out of 5

Hi LamNguyen,

We appreciate your feedback. At SQL Server Magazine, we do keep reader's comments in mind when planning future content.

Thanks!

Megan Bearly Associate Editor, SQL Server Magazine mbearly@sqlmag.com

meganbearly- April 29, 2008

Article Rating 5 out of 5