Has anyone come across any code that simply shows a list of customer's subscription series for a given season including seat locations? Sounds simple in English, but I have such a devil of a time figuring out which tables hook up to what when it comes to ticketing...me am ignorant.
Thanks, Tessiturians for this and all previous help.
BONUS TRIVIA: Nine out of every ten living things live in the ocean.
Matt,
Do you have a SQL job that is running the season ticket update procedure for season 43? It sounds like you don’t.
Here at The Granada we start running the season ticket updates for seasons as soon as they go on sale – we don’t wait until the official “start” of the season – so we can find this information for all seasons – past, present and future.
-steve
Information Technology Manager
The Granada
(805) 899-3000 x 111 (phone)
(805) 899-3081 (fax)
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Matt Gonzales Sent: Friday, June 18, 2010 2:02 PM To: Steve Carlock Subject: Re: [Tessitura Technical Forum] Tessitura Ticketing Tension
No, see, that's the problem. The subscription history table (T_SUBSCRIPTION_HIST) doesn't contain any information for the upcoming season (43).
This always drives me crazy, being that I'm a novice SQL programmer on my best day, and given Tessitura's Byzantine table structure. I simply need the following information for my 2010/2011 Opera Season Subscribers:
EXAMPLE:
customer_no lname series seat 101675 Johnson A OPEN 11 Orchestra Prime A 1225945 Smith A OPEN 11 Orchestra Prime A
Everyone has been helpful in suggesting that I look in the subscription history table which seems to have most of the information I need - for past (okay, and current) seasons. Perhaps the issue as yet unnoticed is that some stored procedure is not updating that table with future subscriptions that have entered the system, indicative of some end of season procedure maybe?
In either case, it shouldn't be a Herculean task to pull this information from its constituent tables into an ostensibly simple report. Or so I believe.
I've certainly been wrong about this sort of thing before...
From: Ryan Rowell <bounce-ryanrowell5634@tessituranetwork.com> Sent: 6/18/2010 2:07:11 PM
Can you get that from your sub history table? (probably lt_sub_hist) I'm not entirely sure what you want for "series" but if you want the package description and like us you have the package code in your sub history you can link back with the pkg_code to t_pkg to get the description.
Does that help?
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
A-HA! I figured as much. I'll handle that right now.