We're looking for any lessons learned or war stories about your T-Stats implementation. Basically, is there something you wish you had known when you were first implementing and configuring Tessitura.
We're amidst implementing Tessitura and T-Stats right now, and we're looking for any advice or pointers on how to make it flow as smooth as possible. Again, we don't want to miss anything in these early parts of the implementation of Tessitura that will hurt T-Stats functionality down the road.
Thanks in advance,
Aaron G
Hi,
The actual installation of TStats was not too bad. Just make sure that you read through all the steps and are comfortable with them. We had a couple meetings with some of the powerusers to determine how some of the config settings should be set. Any questions I had during installation JCA was available to answer them.
Jon
What got me a lot at first was if you make changes (add new elements to the cubes, etc) and redeploy and process the database from BIDS, the roles get blown away and have to be recreated. Whereas if you're just processing from the SQL job that refreshes the cubes, they do not get blown away.
I kept customizing the cubes and processing from BIDS midday to check the changes. Inevitably a few days later a user wouldn't be able to open T-stats and I'd find the roles weren't there. At first it was very Gaslight and I wondered whether I had actually created the roles in the first place, and because of the delay in hearing about it I didn't make the connection to what I'd done. When it happened twice in the same day I finally wised up and asked JCA and got the answer really quickly.