Question on shared report #170 - Cleanup Connections

Yeah, that actually should read:

select      @test_order_no = isnull(min(wo.order_no),0),

      @test_customer_no = min(wo.customer_no),

      @test_value_no = max(datediff(n,wo.first_seat_added_dt,getdate()))

from [dbo].tx_perf_seat x

join  [dbo].t_web_order wo on x.order_no = wo.order_no

where       x.locked_by = @locked_by

group by x.locked_by

Good catch.

-Ryan

From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Steve Carlock
Sent: Friday, October 22, 2010 5:02 PM
To: Ryan Creps
Subject: [Tessitura Technical Forum] Question on shared report #170 - Cleanup Connections

I've just recently installed share report #170 - Cleanup Connections, which is a wrapper around tp_cleanup_connection.  I was looking to use it today during a big on-sale to clean up some leftover web seats but could never get it to work.  In looking at the code,  the following block looks odd to me:

--get test values from web orders table
select     @test_order_no = isnull(min(wo.order_no),0),
    @test_customer_no = min(wo.customer_no),
    @test_value_no = max(datediff(n,wo.first_seat_added_dt,getdate()))
from     [dbo].tx_perf_seat x
join    [dbo].t_web_order wo on x.order_no = wo.order_no
where      x.locked_by > 0
group by x.locked_by

I would think that the where clause should be  comparing x.locked_by to the @locked_by parameter, but I know I don't know enough to be sure.

Is anyone using this report?  Did you have to make any changes?

As always - thanks in advance.

 -steve carlock

Santa Barbara Center for the Performing Arts/The Granada

This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!

Ryan,

Thanks.  Worked like a champ.

A related question.  We had a big (for us) on-sale last week that completely overwhelmed our web site and the seat server.  We kept seeing seat locks that were hours old that would reappear after releasing them.  I went as far as taking the web site down (at the end of the day, of course), waiting longer than the timeout period, and then restarting the seat server before bringing the web site back up.  Almost immediately I had locked seats with a first_seat_added_dt that was about an hour before I took the web site down.  What could cause this?  Do I need to open a ticket for this?  (Things appear to be working fine now, and we are working to increase the robustness of our web site so we don’t have these issues for our next big on-sale).

Thanks!