I'm new to the Ticketing side of things in Tessitura. I've never done anything with Season Manager, Ticketing Setup, Facility Manager, Packages, etc., so forgive me for some newbie questions.
What role does a LIVE to TEST copy play with respect to Rollover and mapping price types from one season to another? Do I really have to perform a series of lengthy LIVE to TEST copies every time I make changes?
And if so, is there any easier way to do the LIVE to TEST copy, maybe automating parts of the procedure into a manually-run job in SQL Management Studio?
Thanks, Tessiturians.
In my experience it is best practice to build your season, packages and rollover sets in LIVE (only build once if you can...), but before you actually run the rollover utility and create orders do the copy of LIVE to TEST. Run the rollover utility in TEST first, so if something blows up you are not stuck cleaning up bad orders in LIVE. In many years of building seasons and running rollovers I have never had to do more than one copy of LIVE to TEST. While I have found errors in the test rollovers, they were small enough that I just fixed them in LIVE and rolled over without re-testing. Depending on your comfort level or the level of error you see in TEST you may want a second copy of LIVE to TEST, but it is much easier to do the copy than clean up bad rollover orders.
Hi Matt:This is one of those 'you pay for in the end what you don't do in the beginning' kind of things. It is probably always going to be worth running a LIVE to TEST copy when you make changes.
You want to make sure the changes took affect, you want to make sure the changes didn't trigger any other errors (new price type isn't connected with fees, etc.).
Any mistakes will live in your system through the end of the new season, and possibly longer than that in terms of historic reporting.
Best of luck,
Mark