The move from 12.1 to 12.1.2

Hi Stacey,

We upgraded to 12.1.2 recently, and all-in-all, it went well and is working for us. We also applied hotfixes HF4 and CLR-OFF.

Here are two issues we ran into - they may not affect you, but I wanted to mention them to you:

(1) Our product catalog in ticket orders when a customer number is loaded is coming up slowly (5+ seconds). If customer is not selected, the product catalog comes up normally. I have an open ticket with Tessitura on this; they are currently waiting for me to perform next steps, but I hope we'll have that one figured out soon.

(2) WP_GET_ORDERS_FOR_DELIVERY stored procedure is an older version of the procedure that was in 12.1. That was not intentional, and I simply applied the 12.1 procedure after consulting with Tessitura support.

I hope that helps.

Thanks,
David

Hello,

We at MAP just did our upgrade to 12.1.2 on Monday..   This article was brought to my attention, and here is what I found:

The TIM I downloaded (on Friday to prepare for Monday's upgrade) contains a script in there for the WP_GET_ORDERS_FOR_DELIVERY procedure. 

The script that alters this procedure (For 12.1.2) has a comments entry in there from 4/22/2013 (RAP).  That is the most recent modification comment.

Meanwhile, I checked for the same procedure alter script in TIM for 12.1.0 (the upgrade prior to this one, which we applied sometime late summer), and indeed there is a more recent comment entry from  6/1/2014 (CWR) in that script.  That is the most recent modification comment in there and I can see the 4/22/2013 comment just before that one..

Anyhow, the 6/1/2004 comment (in the script for the 12.1.0 upgrade, missing in the script for the 12.1.2 upgrade) is as follows:

Modified CWR 6/1/2014 #8514 -- improved performance by removing index hints.  Moved @max_rows_to_return processing to the end.  Also
 changed logic for selecting reprint orders, which is now based on reprint request date, not order date

So indeed it appears there was a performance fix in 12.1.0, however it seems this was rolled back (probably not intentionally) on the 12.1.2 upgrade when it pushed in the procedure without this most recent fix in there.

So now I wonder if I should just go ahead and replace our WP_GET_ORDERS_FOR_DELIVERY procedure with the 12.1.0 version (as David did)???

Can someone from Tessitura chime in on this??

Hello,

We at MAP just did our upgrade to 12.1.2 on Monday..   This article was brought to my attention, and here is what I found:

The TIM I downloaded (on Friday to prepare for Monday's upgrade) contains a script in there for the WP_GET_ORDERS_FOR_DELIVERY procedure. 

The script that alters this procedure (For 12.1.2) has a comments entry in there from 4/22/2013 (RAP).  That is the most recent modification comment.

Meanwhile, I checked for the same procedure alter script in TIM for 12.1.0 (the upgrade prior to this one, which we applied sometime late summer), and indeed there is a more recent comment entry from  6/1/2014 (CWR) in that script.  That is the most recent modification comment in there and I can see the 4/22/2013 comment just before that one..

Anyhow, the 6/1/2004 comment (in the script for the 12.1.0 upgrade, missing in the script for the 12.1.2 upgrade) is as follows:

Modified CWR 6/1/2014 #8514 -- improved performance by removing index hints.  Moved @max_rows_to_return processing to the end.  Also
 changed logic for selecting reprint orders, which is now based on reprint request date, not order date

So indeed it appears there was a performance fix in 12.1.0, however it seems this was rolled back (probably not intentionally) on the 12.1.2 upgrade when it pushed in the procedure without this most recent fix in there.

So now I wonder if I should just go ahead and replace our WP_GET_ORDERS_FOR_DELIVERY procedure with the 12.1.0 version (as David did)???

Can someone from Tessitura chime in on this??