We at Bass Hall-Fort Worth are relatively new to Tessitura, with final go-live scheduled for July 1. We recently contracted with QAS to help with patron addresses, and as part of this contract QAS scrubbed all existing address records.
I want to update the existing address records with the scrubbed addresses, but have a concern:The update requires over an hour to complete in our Test environment. During the update the Tessitura application is (more-or-less) not available to our local users (most queries will time-out).When I "purchase" tickets through our Test web site, the process works but it is slower.
Will this update significantly affect patrons when they attempt to purchase tickets through our web site?I suspect it will, and if so I can re-write the update as a stored procedure and schedule the procedure to execute at an early morning hour. However, I'm not the best at SQL and prefer to manually run the update so I can monitor for any problems.Any thoughts or suggestions?ThanksWendell Baskin
Hi Wendell
I think it will affect your website and you will start to receive odd results.
Personally, if its a one-off, I'd either come in early and take the site down or take the site down after close of play so you aren't affecting many people.
I'm curious what solution QAS have suggested that will work via stored procedures as our version of QAS data isn't in SQL format.
Wayne