Viewing 7 posts - 1 through 7 (of 7 total)
Jack Corbett (1/19/2009)
January 20, 2009 at 9:20 am
i found the problem. some one broke my source table and so i had duplicates. after cleaning this table my stored procedure had no errors.
January 20, 2009 at 9:06 am
i have build my stored procedure but i get always this error:
Msg 2627, Level 14, State 1, Procedure import_DB_PARAM_HIST, Line 14
Violation of PRIMARY KEY constraint 'PK__DB_PARAM_HIST__29ADC38E'. Cannot insert duplicate key...
January 20, 2009 at 8:39 am
yes i would, but then i can't use a stored procedure because my transformation output can't be an input for the stored procedure, right?
January 20, 2009 at 7:13 am
if i say that i have to transform some data types you will killing me, right? 😉
January 20, 2009 at 7:01 am
Thanks for your replay. i need a very hight performance solution because i have to handle a destination database with ca. 7tb. so my tables are very large.
Could i...
January 19, 2009 at 2:48 pm
Viewing 7 posts - 1 through 7 (of 7 total)