Subscription Question

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'.

Parents
  • Former Member
    Former Member $organization

    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

    Information Technology Manager

    The Granada

    (805) 899-3000 x 111 (phone)

    (805) 899-3081 (fax)

     

Reply
  • Former Member
    Former Member $organization

    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

    Information Technology Manager

    The Granada

    (805) 899-3000 x 111 (phone)

    (805) 899-3081 (fax)

     

Children