title: SSIS script component *bug* – Column data type DT_DBDATE is not supported by the PipelineBuffer class
body: <p>Does anyone know exactly why these types of issues happen using a script component that can be “fixed” by deleting and re add the same code to make fix this type of issue?  Why would metadata change when you delete and re add code? what happens inside the engine when this happens? What kind of issue could it ever fix to delete and re add a script component, copy the same code and rewire it? </p>
  
  <p>I can reproduce at will with the following steps: </p>
  
  <ol>
  <li>Took a working package with a script component and two output buffers. The script component has additional input columns and output columns setup for the second output buffer that are not being populated yet by the source query (OLE DB source SQL command) yet.  Only one column is being populated in the second output buffer from the source query . </li>
  <li>Copied in a new source query with additional columns for the second output buffer.</li>
  <li>Run the package. Get the error message Column data type DT_DBDATE is not supported by the PipelineBuffer class.</li>
  <li><p>Comment out the two lines for the second output buffer, run the package, the package runs successfully:</p>
  
  <p>RedactedOutputBuffer.AddRow();</p>
  
  <p>RedactedOutputBuffer. RedactedColumnName = Row. RedactedColumnName;</p></li>
  <li><p>Uncomment the <strong><em>same</em></strong> two lines. The package still works. <strong>So the package is now exactly the same as when it did not work.</strong> </p></li>
  </ol>