September 30, 2015 at 7:19 am
ok following table
create TABLE dbo.ABC
(
[ID] [bigint] NOT NULL,
[NAME] [nvarchar](255) NULL,
[CREATED] [datetime] NULL,
[UPDATED] [datetime] NULL,
[StartDate] [datetime] NOT NULL,
[EndDate] [datetime] NULL,
CONSTRAINT [pk_ABC_ID] PRIMARY KEY CLUSTERED
(
[ID] ASC,
[StartDate] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]
Now I got an ssis with a SCD in it with the business key on ID and all other columns are Historical changes,
start- and enddate indcate validity of the record.
so today I did an import of new data & for some records where there are no changes what so ever (and I double & triplechecked) new records were created.
Anyone got any clue what I've could have done wrong.
I did the primary key ID,Startdate cause ID itself is not unique.
September 30, 2015 at 11:32 pm
Ok I think I've found the issue,I checked the scd and look at this message
Cannot map columns of different types.
Column 'CREATED' is of type 'System.String' and column 'CREATED' is of type 'System.DateTime'.
Yet when I look in sql, the datatype of CREATED in the staging table as the live table is datetime,looking at the advanced output of the ole db source for the dataflow it clearly state column created to be a database timestamp, so those should match.
Ok that was indeed the issue,when moving the packages from dev to staging the scd broke on a few columns,not sure why though as their datatyps didn't change
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply