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

    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)

     

     

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

Reply
  • 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.

Children
No Data