Hi,
We recently virtualised our servers and set up T-stats on our test database for testing. I would like this to now look at live data but I have had some queries and issues raised by our external IT company.
From what I have been told we have three options at this point:
1. leave t-stats on our test server but point it at the live database.
2. leave it connected to our test database but refresh this more frequently (I am not keen on this option)
3. Install on our live database sevrer.
We would then load all of the data once per week and refresh t-stats daily.
I am wondering if anyone who has T-stats could let me know what option they went with? Also I have been asked if we would like to change the frequently to load all of the data fortnightly or monthly to reduce resource usuage - has anyone else changed their frequency?
Thanks for your help,
Katrina
We do it the same way, for pretty much the same reasons.
Kirk Mortensen
Database Administrator
TheatreWorks
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Ken McSwainSent: Wednesday, September 28, 2011 9:15 PMTo: Kirk MortensenSubject: RE: [Tessitura Technical Forum] T-stats installation query
Hi Katrina
Our setup over here is similar to Teresa’s
Ie The T-Stats data sits on the secondary db, we do a full load weekly, and an incremental load nightly.
We wanted to keep as much reporting load as possible off the Live server, to maximise its performance on operational duties, which is why it’s not on that one.
The loads run at midnight or 0100 (after the backups, and some critical related overnight jobs like ticket history updates have finished), to try and keep them out of the way of other things. They probably clash with overnight scheduled reports at times, but since we put extra grunt into the db servers, we seem to cope happily with the loads now.
________________________________Ken McSwain
Systems and Technology Manager
Australian Chamber Orchestra
ken.mcswain@aco.com.au
Ph +61 2 8274 3833 :: Mob +61 418 659 360 :: Fax +61 2 8274 3801
PO Box R21, Royal Exchange NSW 1225
2 East Circular Quay, Sydney NSW 2000
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Teresa DeanSent: Thursday, 29 September 2011 10:55To: Ken McSwainSubject: RE: [Tessitura Technical Forum] T-stats installation query
Katrina,
I have T-Stats installed on my Test server and it points to my Live server. I haven’t had any issues with it. My data refreshes nightly and I do a full load weekly of the data.
Teresa
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Katrina RiddleSent: Wednesday, September 28, 2011 7:49 PMTo: Teresa DeanSubject: [Tessitura Technical Forum] T-stats installation query
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!
Explore the 2012 season at aco.com.au/season2012This email is confidential. If you are not the intended recipient you must not disclose or use the information contained in it. If you have received this email in error please notify us immediately by return email and delete the document. The ACO is not responsible for any changes made to a document other than those made by the ACO or for the effect of the changes on the document's meaning. The ACO accepts no liability for any damage caused by this email or its attachments due to viruses interference, interception, corruption or unauthorised access.
We needed the rich reporting aspects of T-Stats so we do nightly incremental updates and a weekly full load. We haven't found any performance issues due to this. We do these at night after our backups complete.
I think you will find that this keeps things very up to date for reporting but minimizes the production database being over-utilized.
Thanks,
Dave AltonCIOCenter Theatre Group