Greetings, Tessiturians.
It's another slow summer day in the off season. Perfect time for silly questions like:
I know that Subscription information from seasons past (including the current season, though technically not over yet) can be found in T_SUBSCRIPTION_HIST. But, where do I find subscription information (including data like the SERIES_NO and LOCATION) for upcoming seasons?
I'm assuming the information gets updated into the T_SUBSCRIPTION_HIST by some stored procedure call at the appropriate, pre-designated times, which is why my development contact didn't get next year's information like she wanted from Output Set Builder.
Any takers? Or too early in the morning for silly questions from people that don't like going through reams of boring manuals before lunch?
Thank you in advance, as always, for your assistance. Crowd surfing is my Tessitura research tool of choice.
BONUS TOOL-RELATED TRIVIA: The opposite end of the striking face of a hammer is called the 'peen'.
We have 3 procedures that run nightly with the season id
dbo.LP_UPDATE_SUBS_HIST
dbo.LP_UPDATE_SUBS_HIST_NEW
dbo.LP_UPDATE_SUBS_HIST_NONFIXED
Marty
Matt – We have a process in place for the Ticket Office to notify IT whenever they build a new season so we can add it to the appropriate history jobs (season ticket and/or single ticket). First workday in July I go through and update the jobs to get rid of last season (our fiscal year ends June 30). This keeps everything as current as we can for lists and extractions.
Marty – Would you be willing to share your stored procedures? One of the things on my (very long) list of things to do is figure out a way to add non-fixed packages to our subscription history in a way to keep everyone happy. Thanks in advance.
-steve carlock
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
In the job that updates lt_sub_hist for us we've got a cursor that makes it so it'll run for any active season, which may not be what you want, but it is handy for not needing to manually add new seasons when they're created. Worth considering.
Matt - In the past, I have had to make the same changes that Steve mentioned. Updating the jobs to include new seasons. Now that I have more organizations to manage that was looking a little overwhelming, so we converted the job to work on a cursor that pulls all of the active seasons and updates them. Much simpler and doesn't require annual maintenance.
I put the file on my Tessitura Profile. The procedure is from Andrea Crain of the Chicago Shakespeare Theater.
Hi Matt,
I’m going to try and not take that comment about boring manuals personally. J Besides, I don’t think you would have found the answer you were looking for anyway.
I just wanted to jump into the conversation to make a little clarification. The T_SUBSCRIPTION_HIST table is generally not used. It is vestigial piece of Tessitura evolution, kind of like an appendix. The subscription history you find on the Ticket History tab of a constituent record is usually stored in the LT_SUB_HIST table. It’s an LT table because it is customizable and frequently customized. As others have mentioned, that table is updated by a scheduled procedure and you need to add in new seasons to the procedure parameters as they are added.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com
Marty – Thanks! (and thanks to Andrea as well).
Amanda/Levi – I’ve thought about using the cursor method as well, but we tend to have exceptions to the rule every year so for us it’s the same amount of work. What I really want to do (as soon as I can find the time) is set up my LTR_SEASON table so that when the ticketing folks create a new season they can update that table with which of the history scripts should include it and the constituencies they would want as well. (Now that I think about it, maybe I should put this in as an enhancement request to expand TR_SEASON to include this for local use – it already has the flag for EIS now, adding a couple more shouldn’t be that hard……)
-steve
Steve,
Would it work to distinguish them through Season Type? Set up a couple of new rows in tr_season_type and drive the cursor from there?
Levi,
Season type would probably work now – we’re still new enough that things kept cropping up and the season types were still in flux. I’ll mention that at our next Tess Team meeting and see if we think it’s stable enough now.
Thanks.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Levi Sauerbrei Sent: Thursday, June 17, 2010 12:26 PM To: Steve Carlock Subject: RE: [Tessitura Technical Forum] Subscription Question