• Replies 6 replies
  • Subscribers 359 subscribers
  • Views 35 views
  • Users 0 members are here
Related

Version 11 release

Boann Petersen
$organization

Thank you for the very informative webinar this morning on what to expect in Verion 11 and beyond. 

Our Tessiutra team has looked our calendar over and have decided the best time to upgrade our live system is in the first two weeks of January.  However, when we decided this we thought the general release would be in November and we would have a full 6-8 weeks of testing and training.

With the complete understanding that it is all subject to change, can you share if you expect the general release to be in early December or later in the month?  We would ideally still like to do the upgrade in January, but if that needs to change we would like to figure it out now. 

Thanks,

Boann

  • $organization

    I feel the pain we have our date set to be Dec 27th or 28th.  We are also preparing contingency plans and are planning on moving our test system to the Beta the day it is released.

     

    Thanks,

     

    Dave Alton

    CIO

    Center Theatre Group

    www.centertheatregroup.org

     

    dalton@centertheatregroup.org

    o:213-972-7539

    40email

     

    From: Tessitura Next Generation Forum [mailto:forums-nextgeneration@tessituranetwork.com] On Behalf Of Boann Petersen
    Sent: Wednesday, October 26, 2011 11:37 AM
    To: Dave Alton
    Subject: [Tessitura Next Generation Forum] Version 11 release

     

    Thank you for the very informative webinar this morning on what to expect in Verion 11 and beyond. 

    Our Tessiutra team has looked our calendar over and have decided the best time to upgrade our live system is in the first two weeks of January.  However, when we decided this we thought the general release would be in November and we would have a full 6-8 weeks of testing and training.

    With the complete understanding that it is all subject to change, can you share if you expect the general release to be in early December or later in the month?  We would ideally still like to do the upgrade in January, but if that needs to change we would like to figure it out now. 

    Thanks,

    Boann




    You were sent this message automatically by www.tessituranetwork.com because you subscribed to the Tessitura Next Generation forum email notifications. You may reply to this message or visit the site to reply to the post above. If replying via email, please consider deleting the previous message text before sending to help with readability on the site. Thank you!

  • $organization

    Hi there.

    We were unable to attend the session today and planned on sharing the posted webinar. Can you tell me what you learned regarding the release date?

    Thanks

    Susan

  • $organization

    Hi there.

    We were unable to attend the session today and planned on sharing the posted webinar. Can you tell me what you learned regarding the release date?

    Thanks

    Susan

  • $organization in reply to Susan Hayes

    Boann,

    The answer is (as you might expect) it depends on how things go with the BETA testing, which we expect to start in mid-November. I'm afraid we cannot be any more exact than that without being completely speculative.

    Susan,

    Here's the timeline we announced on the webinar today:

    * Sept - October 2011: ALPHA testing with selected users
    * November 2011: BETA testing with additional users
    * December 2011: General release of v11
    * Upgrade deadline will be at least 6 months after General Release

     

    Thanks,

    Andrew

  • $organization in reply to Andrew Recinos

    Thank you for confirming what I expected.  I am sure that I am not alone in wishing to hear more details as soon as they are available.  In the mean time we will work on the items we can with the toolkit and try to wait patiently.... 

    Thanks,

    Boann

  • $organization in reply to Dave Alton

    Dave, 

    During the webinar Q&A you had asked how others were dealing with numerous inactive accounts with N1+N2, or identifying N1+N2 accounts that should become inactive.  Your concern was that additional household accounts would be created unnecessarily, yes?

    We have a data hygiene group that meets regularly and one of their tasks is to agree upon the characteristics of what we call "shell" accounts.  In essence they would be accounts added before a certain date with no transaction history.  We inactivate them en-masse.  For the migration I will be suggesting we purge N2 info from those account so that household accounts are not created.  That would mean removing the N2 data for those accounts from t_customer, as well as changing the N2 flags to "both" for attributes, associations and constituencies.  I'd start by creating a list of these patrons and processing each cleanup step off that list.

    I'd be happy to share the cleanup script I create for that purpose once we get to that point.

    Here is an example of a list builder query we'd use to identify active shell accounts, it allows for an exclude list.  If you want inactive to be included as well remove [ IsNull(a.inactive, 1) = 1  AND] .

    SELECT distinct a.customer_no

    FROM t_customer a (NOLOCK)

    WHERE IsNull(a.inactive, 1) = 1 

    AND A.create_dt >   DATEADD(YEAR, -2, GETDATE()) 

    AND NOT EXISTS (select * from TX_CONST_CUST where TX_CONST_CUST.Customer_no = A.Customer_no ) 

    AND NOT EXISTS (select * from T_SUBSCRIPTION_HIST where T_SUBSCRIPTION_HIST.Customer_no = A.Customer_no ) 

    AND NOT EXISTS (select * from T_TCK_HIST where T_TCK_HIST.Customer_no = A.Customer_no ) 

    AND NOT EXISTS (select * from T_CONTRIBUTION where T_CONTRIBUTION.Customer_no = A.Customer_no ) 

    AND NOT EXISTS (select * from TX_XREF where TX_XREF.Customer_no = A.Customer_no ) 

    AND NOT EXISTS (select * from T_LIST_CONTENTS 

    where T_LIST_CONTENTS.Customer_no = A.Customer_no

    and T_LIST_CONTENTS.list_no = 14696)

     

    Chris