Good point about the PK value. I did it with the UNID of the Notes doc as it's then easier to tie them together to other tables in a Parent-Child manner. I guess LongInt could be used as the PK and still join the tables on the UNIDs...
Speed was never really a factor though. The target SQL tables are just temporary containers for the (E)xported data, from where it's (T)ransformed before (L)oading in to the target platform (ETL).
Good point about the PK value. I did it with the UNID of the Notes doc as it's then easier to tie them together to other tables in a Parent-Child manner. I guess LongInt could be used as the PK and still join the tables on the UNIDs...
Speed was never really a factor though. The target SQL tables are just temporary containers for the (E)xported data, from where it's (T)ransformed before (L)oading in to the target platform (ETL).