Updating Ticket History issues

Hello all - 

So the last few days our localized "update ticket history" table procedure has taken over a day and half to update our history table.  So... I know the proc is working at least!  But a proc that runs for 1 day, 12 hours + doesn't do us any good with as many exchanges we have.

The localization we have is two fold and it's cosmetic only: We like our seat location to read "Sec: 1, Row A, Seats 101,102" rather than the Tessitura standard of (what I believe to be) '1 A 102,103'.  to get that, all i did was copy the FT_HISTORY_LOCATION and add in the text for "Sec " and "Row ".  

The second localization is simply the TP_UPDATE_TICKET_HISTORY proc modified to pull it's location data from the localized Function Table rather than the standard Function Table.

So maybe it's pulling too much data?  We do have 6 seasons running with a 14 month date range (to catch the earliest of sales).  So the questions here are: 

- Do you break out your jobs to one for each season?

- How many days back do you go? We used to go 30 but I'm cutting it to 10 now that the proc is taking so long in hopes that helps

- How long does your proc usually take?

Any input is appreciated so i can see if I'm just way off the course or if I need to mod these jobs from here on out to go by season individually.  Thanks!

RJ