SSIS 2008

[shoubs]

OLEDB source

We are using SQL Task, not OLEDB source. It didn't occur to me even that you could insert into a source (I thought I was for extracting data - so it looks like source and destination are almost the same thing),

So SQL TASK is what I am using in the CONTROL FLOW.

[Moderator]

I have sent you a fixed build (with fix for DateTime corruption issue).

[shoubs]

I have sent you a fixed build (with fix for DateTime corruption issue).

Thank you, please see my email for more details (TRUNCATE TABLE no longer works).

[shoubs]

Here's a question you might know a quick answer to: I'm using retain connection for a couple of the querys (so I can get an id of a serial col) but the connection stays open. I want to close that connection to the database (or all connections) so I can do a VACUUM FULL FREEZE ANALYZE at the end of my process. Any idea's?


The weird problem I'm having is something to do with the data - there are 211 rows, if I reduce the number to 1, it works. There must be some data problem somewhere, and the provider may not be handling the exception?

There appears to be a lot of cells with '' as the value (thats two single quotes) or problems with extended characts such as @ and . (dot) That wouldn't be a problem would it?

[Moderator]

I cann't answer it from top of my head. Let me experiment with the connection a little bit...

I do not exclude chance that there is a bug that we and our existing clients have not discovered yet. Could you provide more details about your insert/update scenario? Could you narrow the issue to smaller number of records and possibly send us some that we could use for reproduction?

Thank you very much!

[shoubs]

Could you narrow the issue to smaller number of records and possibly send us some that we could use for reproduction?

Thank you very much!

I found it - see the email I sent you, Could it be a problem with a NULL constraint - one field has a value of NOT NULL and has two single quotes in it. When you select this it appears to show NULL.

[Moderator]

Yes, the defect is reproducible and we are working on the fix.

[shoubs]

Yes, the defect is reproducible and we are working on the fix.

Cool, what was the problem?

[Moderator]

The issue was caused by bug in formatting data for bulk insert. PGNProfiler shows following error during data flow execution:
---------- Client SQL ------------
PQputCopyData
---------- Error ---------
ERROR: null value in column "groupname" violates not-null constraint
CONTEXT: COPY tmp_groupowner, line 1: "172|||||||||||0|0|01/01/2007 12:00:00|0|f"

I could not initially reproduce it because I did not use BULK_METHOD=COPY in connection string. Will send you fixed build shortly.

[shoubs]

Will send you fixed build shortly.

Thanks. Are there any instructions on useing the profiler? I haven't looked at it to be honest.