Transcend v.3

We are currently on v2 of Transcend (v11 of Tess) and our bank is "switching us over to Nashville" which requires version 3 of Transcend.  We are currently on Transcend v2 (but live on v11 of Tessitura).  So I'd also like to know of anyone who has done this upgrade successfully.

The specific issue is that according to Intrix support, their upgrade procedure is to create a new SQL Server instance.  This is because the upgrade from 2.x to 3.x is not actually an upgrade.  It's a fresh install that creates the same db names as the old ones (TPAU and TPAUARCHIVE).  Brilliant.  Given the advantage to keeping all our SQL Servers on the same instance, I wonder if anyone has seen any challenges in creating the new databases somewhere, then restoring them back to the proper place alongside the Impresario db.

Additionally, if anyone knows if there is any documentation out there specifically on Tessitura v11 to Transcend 3.x integration (are there changes to config files?), I'd greatly appreciate it.

Thanks

Michael

Michael Reisman
Director of Information Technology
The New 42nd Street, Inc.
mreisman@new42.org
646.223.3069

We upgraded to transcend v. 3 several weeks ago.  Naturally there were some issues, but mainly they were due to the timing of the batches that we thought we had set up for autosettle and had not.  For example, one merchant settled at our normal midnight but the other one was not included.    

The changes to cc_server.ini were minor, I got the from Tess support ahead of time.  We had one problem that our transactions were going into purchase/settle mode instead of auth/held/release., changing the CC_ALLOW_PREAUTH setting in t_defaults fixed that.  

I detached the tpau databases and moved to different server and then did the clean install.  Simple and fortunately we normally do not need to access history but if we need to we can.  

It  took awhile for the Ticket Office to get everything balanced but they did.  We have one open item and that is the swipes are causing an error.  We decided to wait until all of the other issues were cleared up (and have a little break) to tackle that.  I have a ticket open with Tess and I'm sure it will be closed soon.

Hope this is helpful.

We upgraded to transcend v. 3 several weeks ago.  Naturally there were some issues, but mainly they were due to the timing of the batches that we thought we had set up for autosettle and had not.  For example, one merchant settled at our normal midnight but the other one was not included.    

The changes to cc_server.ini were minor, I got the from Tess support ahead of time.  We had one problem that our transactions were going into purchase/settle mode instead of auth/held/release., changing the CC_ALLOW_PREAUTH setting in t_defaults fixed that.  

I detached the tpau databases and moved to different server and then did the clean install.  Simple and fortunately we normally do not need to access history but if we need to we can.  

It  took awhile for the Ticket Office to get everything balanced but they did.  We have one open item and that is the swipes are causing an error.  We decided to wait until all of the other issues were cleared up (and have a little break) to tackle that.  I have a ticket open with Tess and I'm sure it will be closed soon.

Hope this is helpful.