Hi all,
After building the 2010 season I've been told that one of the shows dates has changed by two weeks, is there any reason not to simply run an update like this example?
update t_perfset perf_dt = dateadd(dd,-14,perf_dt)from t_perf where prod_season_no = ???
I don't think it matters but these shows have not been seated yet but are built into performance groups and packages.
Thanks!
Somehow I missed that you were looking to save time using SQL. In that case, I’m not sure of any caveats. I’m not an expert on the database side of the system. It seems like it should be o.k. Definitely try it in your Test system first, and maybe open a help ticket so those wiser than I in this area can weigh in on anything to look out for.
Kevin Sheehan
Documentation & Learning Resources Specialist
Tessitura Network
1 888 643 5778 ext 329 Office
ksheehan@tessituranetwork.com
ooh, good one Amanda!My price types & web publish dates are usually open ended but good call about all those things.I think unless someone tosses up a red flag I'll do the update on perf_dt but do the MOS in season mgr.
Thanks Kevin and Amanda for the feedback!
Ryan -
I do this all the time. I know you posted this a long time ago (catching up on my forum posts *finally*), but just to let you know that besides the noted start/end dates, the only other dates I watch out for are on calendar/on web dates as well.
One other thing I watch for on my implementation is any "funny" shows (i.e. dummy perfs that we have set to an outlying date). These are normally a set date and I don't want to bump them forward.
- Heather
One other thought is source code end dates if you have anything using a special source.
Thanks everyone!
Thankfully these were freshly created shows so there wasn't much that needed updating but this thread and all the input will come in handy again I'm sure.
Cheers!