Hi All,
We are on tessitura version 12.5.1. We are planning to upgrade our sql server to 2016. Currently we are using sql server 2008 R2.
I am just doing some ground work before I start my upgrade.
I talked to tessitura they said it should be at compatibility level 2012. Apart from this was there any changes or problems you have faced when you upgraded your tessitura SQL server version to 2016?
It will be really great if you can share the issues you have faced in this process and how you have solved the same.
Thank You,
Shivani
I thought the compatibility level is 2014 for the maximum and 2012 for the minimum. We use SQL2016 as our SSRS reports server. The only thing there was Visual Studio 2015 data tools for our solution files. We have not ran into any issues with 2016 for SSRS.
SQL server 2016 is quite solid and fast. We have had no problems. Although I am puzzled they suggested 2012 mode. We were instructed to run in 2014 mode and that is preciously what we have been doing with no issues at all. Hope this helps!
I haven't. I run SQL 2016 here at the Walton Arts Center and running 2012 compatibility. I haven't run into any problems per se.
On Feb 21, 2018 1:42 PM, Shivani chamakura wrote:
[cid:Tessitura_2D00_Network_2D00_logo_5F00_1500x421-png_2D00_150x42-png@tessituranetwork.com] Update from Tessitura Network
[cid:default-png_2D00_70x70x2-png@tessituranetwork.com]
Shivani chamakura
View online
You received this notification because you subscribed to the forum. To stop receiving updates from only this thread, go here.
Flag this post as spam/abuse.
[https://community.tessituranetwork.com/notification/read?NotificationId=7077c790-efcd-4bbd-9a99-c5afbcce9982]
Thank you all for the reply, this information is good for me to start with my upgrade.
Hi Robert and Shivani,
We have SQL server 2016 installed on a new Azure VM we setup to test Tess v14.1. No issues so far with anything but we have not connected the v14 test environment to TSTATS or RMA yet. We're running in SQL server 2012 compatibility mode. There was a hiccup we came across with the database encryption key while doing a copy of the databases from a different environment to the v14 env. This was resolved by detaching the databases and deleting all the users that had been copied (including tessapi), then doing another copy down and later recreating the database encryption key.
When we upgrade our other environments like Test, Staging, and Live to SQL server 2016, do you know if it's recommended to create a new server and then install there, eventually moving everything from the current environment to the new one?
We planned to do a side-by-side installation on the current Staging server with no changes to hardware other than maybe adding a new drive for extra space. Does this sound ok or should we install on a new server (which would have a newer OS) and then migrate everything over?
Hello,
We recently upgraded our TEST environment to SQL Server 2016 (Tess V12.5.1). Things are working except we are getting an unauthorized 401 error when running reports in the application or WebReports. I'm wondering if you had a similar error. Note: we installed reporting services from a user's profile instead of Administrator.
Thank you,
Lou Ann
did you implement azure for tessitura?