Hi,
We recently came across the realization that there was a patron who received 2 copies of a mailing and after investigating noticed that her ticket history from her household record was different than her individual record. The reason why this happened is because we pull our lists of previous season buyers based off of ticket history tables which are updated nightly job. All I can figure out is that this issue happened because at one point she had an individual account that began to accrue order history and because her data wasn't moved into her household account until 3 seasons ago, the procedure we run nightly to identify order history and move to the ticket history tables is only looking at the past 3 seasons.
We are now a little worried thinking that this issue may also exist in other households/individuals who were merged after the season entered as a parameter in the SQL job. I'm being asked to "quantify" this as well as fix the problem.
My question is: I'm curious as to why the job would not be processing all past seasons and not just the most recent 3 seasons. This may also be a moot point as v12 ticketing history tables all need to be changed, but I wanted to ask if anyone else has had anything like this come up before before I go face first into updating history tables from 2007 thru 2012. Eek.
When I am in Test and I run the procedures from the nightly job one season at a time, this patron's data is updated accurately. (Meaning, the ticket history data from her individual record disappears and instead appears in her household record because that is where her data is now being stored). This is what we want, but I am not sure why this wasn't done before and I don't like messing with ticket history tables unless I know what I'm doing.
Does anyone see any reason as to how this would not work or should I probably just wait until v12 in Live before updating any of these histories since they will be changing anyway?
Thanks,
Tiffany Evans
Database Coordinator
Huntington Theatre Company
Boston, MA