Transcend v.3

We also had to upgrade to Transcend v.3 because of a bank switch which changed our processor to Nashville, about a year ago.  The Transcend v2 to v3 upgrade had some hiccups, but Intrix tech support talked us through those successfully – and yes, we needed a new instance of SQL for the new TPAU databases, which is a bit of a pain.  I haven’t restored them back to my main instance, but may do that with our upgrade to Tessitura v.11.

I will say, however, that we’ve found Transcend v.3 to be a bit “quirky”.  We’re set to auto-settle every night at midnight, which it does – except for the last couple of transactions each night, which for some reason don’t settle, so they wind up in the next day’s batch (which makes our Finance office fairly crazy). Then there are the nights (once or twice a week) where the batch simply doesn’t close at all and I have to go in and manually force a close.  Because processing with Nashville actually closes the transaction when it’s submitted, this is really mostly an internal bookkeeping issue (the transactions have already hit the bank), but it’s very annoying.

Then there are the times when one of the Nashville URL files will have its contents mysteriously blanked, disrupting processing until I go in and manually copy the data from another file and edit it, then restart the services.  This has happened at least twice. 

We had no issues at all with Transcend v.2, so I don’t know if the problem lies with v.3 or with Nashville, or with communication between the two. I hope you don’t have the same issues we’ve had, but I’ll be interested to hear how you get on.

Jeanne

Jeanne DeVore

Technology Manager

Chicago Shakespeare Theater

jdevore@chicagoshakes.com

312 595-5603

www.chicagoshakes.com

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 also had to upgrade to Transcend v.3 because of a bank switch which changed our processor to Nashville, about a year ago.  The Transcend v2 to v3 upgrade had some hiccups, but Intrix tech support talked us through those successfully – and yes, we needed a new instance of SQL for the new TPAU databases, which is a bit of a pain.  I haven’t restored them back to my main instance, but may do that with our upgrade to Tessitura v.11.

I will say, however, that we’ve found Transcend v.3 to be a bit “quirky”.  We’re set to auto-settle every night at midnight, which it does – except for the last couple of transactions each night, which for some reason don’t settle, so they wind up in the next day’s batch (which makes our Finance office fairly crazy). Then there are the nights (once or twice a week) where the batch simply doesn’t close at all and I have to go in and manually force a close.  Because processing with Nashville actually closes the transaction when it’s submitted, this is really mostly an internal bookkeeping issue (the transactions have already hit the bank), but it’s very annoying.

Then there are the times when one of the Nashville URL files will have its contents mysteriously blanked, disrupting processing until I go in and manually copy the data from another file and edit it, then restart the services.  This has happened at least twice. 

We had no issues at all with Transcend v.2, so I don’t know if the problem lies with v.3 or with Nashville, or with communication between the two. I hope you don’t have the same issues we’ve had, but I’ll be interested to hear how you get on.

Jeanne

Jeanne DeVore

Technology Manager

Chicago Shakespeare Theater

jdevore@chicagoshakes.com

312 595-5603

www.chicagoshakes.com

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