i'm hoping for an easier softer way...
We've been using interests in tessitura since close to our beginnings, which is only 4 months, but weight interests on a 1 ticket to 1 point scale.
i'd now like to get around to applying weight to the ticket history i imported!
Naturally, i'll need to do some fancy footwork to get the info even close to what the conversion doc says for TX_CUST_TKW
But even if i did, the BCP utility doesn't want to update the data, as i get a duplicate key error if there is already a value...
So Plan B; import it in the same format to a staging table, then write my own update sql...
thought C:
Could i make a table say ltx_tkt_hist_tkw with ltx_tkt_hist_tkw.event and ltx_tkt_hist_tkw.interest_ID
then run a procedure for each row/ticket in LT_TKT_HIST before we lauched interests where event_desc = ltx_tkt_hist_tkw.event, update tx_cust_tkw with 1 weight where interest = ltx_tkt_hist_tkw.interest_ID
~~~~~
Thought C came to me as i was posting this....other thoughts or opinions are welcome. i'll let you know if i come up with a solution!
So, I worked it out.
I first went back to my LP_INTERESTS_WEIGHTED proc, and noticed that it wipes all interests and recalculates all interests nightly, based on t_order data. But my last thought was on the right track, i just needed to associate an interest (tkw) to events prior to our implementation.
I made a cross reference table to join perf_names to ticket history and associate the particular interest for that event.
then I updated my Proc to UNION ALL and Sum the weight of equal interests.
Once i fully populate my LTX table, i'll be able to do some more thorough testing, but a quick test seems like it is all summing as expected.
here is the SQL:
/******************************************************************************************