ok, i understand now. Thank you for help in placement of the debug statement.

Now, I'm trying to deconstruct the sproc myself and getting tripped up on how the actual insert...

Dev, I did this already.

I executed the stored procedure and then the query.

Will you kindly explain you initial point, so that I can understand where you were going with it?

Thanks Dev, like this? I added Print statements for the variables. I do not understand the purpose of @DELIMITER or have never seen WHEN used in SQL statements. Nevertheless....see...

I have made a copy of Narayana's sproc on my Northwind db. Also, I've made two copies of Employees table calling them Employees1 and Employee2.

When I exec the...

Well, that there was a smokescreen and it is now being handled (ahem, null). Actually, I am puzzled why I have to handle the nulls between staging and destination,...

Hi Charmer,

Yes, the error is:

[OLE DB Destination [119]] Error: There was an error with input column "Copy of POAmountLC" (219) on input "OLE DB Destination Input" (132). The column status...

Here's whats exactly what is coming in and going out at each data flow task.

OLE DB Source

external column numeric [DT_NUMERIC] 15, 2

output column numeric [DT_NUMERIC] 18,0

Data Conversion

input column numeric...

Yes, thanks for replying.

the data source is a SQL staging table which contains the column that is needed in the target table. This particular package is bringing over other...

I have one more problem....but I don't want to double post. However it is at this link.

http://www.sqlservercentral.com/Forums/Topic1218249-148-1.aspx?Update=1

:rolleyes:

Ah yes, Charmer. It was simple and you are correct.

CHA CHA CHA. It WAS a constraint. Those darn Nulls get me every time.

I hope I have finally learned....

But Guess What, Charmer? I have another problem and I bet you can help me 🙂

Dataflow tasks are as follows:

OLE DB source -> OLE DB destination

The source is a...

conclusion to problem: I believed that OLE Destination output was overwriting destination table, but it was not. Once I truncated the destination table I saw that the import went smoothly...

Hi Jeff. Well, I thought my OLE DB output was overwriting destination table each time I ran the package but I was wrong. When I truncated the destination...

OK.:blush:

Jeff,

would you consider looking at one more issue? I just added another column to the excel source so that it would map to an existing varchar (15) column on...