I hope I'm posting on correct board. I'm having a problem with our Update Singles History report. It is including package history in with performance history and is really throwing off our extractions for specific performances. Can anyone help with this? See below for how we set up the job.
exec LP_UPDATE_TKT_HIST @season_no = 31 ,@start_dt = '9/1/2000' ,@end_dt = '5/31/2015' ,@skip_past_perfs = -1 ,@constituency = 19
Without looking at the guts of your LP_UPDATE_TKT_HIST this is speculation, but I'd guess that it isn't limiting to single tickets. I know our procedure of that name updates all tkt history, and then separately, sub hist contains the subs. So for us it's always a matter of either limiting on price type category in the extraction, or suppressing subs first in thwe extraction.
If you want that local table to really only reflect singles, you probably need to add some sort of price type category limitation in there. I'm guessing constituency 19 might have something to do with STBs? That might be throwing it off as well. If you have subscribers who purchase single tickets to other things, then depending on how your update procedure works (or how that constituency is updated), you may be getting all the subs' tkt history if the sub purchased a single ticket at some point.
Along with Amanda I'll chime in that we do update our ticket history with all performances (subs and single ticket buyers) and then when you are doing a list or extraction that you don't want subscribers you'll need to put in a 'Subscription Season' does not have 'Your season here'. This is assuming that you populate your subscription history tables.
I wasn't quite sure of what you meant by 'including package history'. Do you mean it is including individual performances in a package? Or do you mean that it is include the package itself?
Don't think think of 'Performance History' as single ticket history - it is just what it says, a record of all PERFORMANCES that people have gone to, sub and singles alike. The Subscription History radio tab is (usually) a record of the PACKAGES that subs have. This way you can pull lists of subscribers who have a certain package type and came to a certain show. Or exclude those people. It becomes much more flexible.
The caveat here is that everyone's ticket history procedure can be different, so anything we say could be completely wrong for your organization depending on how that procedure has been set up.
HTH,
Heather