Ticketing History for Development Prospects

My Development team is embarking on a campaign to endow our Chamber Music performances.  For background, we are a performing arts festival and our chamber music series consists of eleven separate programs with three performances each.  Here are the criteria they are looking for:

  1. Purchased tickets to at least four performances of Chamber Music at 2016 Festival (Each festival year is season and Chamber Music as a whole is a production season) 
  2. Purchased tickets to Festival at least five years (each year is a season)
  3. Not already listed as a chamber subscriber (constituency)

We do not utilize subscriptions at this time; it's something I want to work with our Patron Services Manager on for our 2018 Festival.  That is to say all tickets are sold individually.  We don't use packages; there is a price type of Chamber Subscriber for each performance.

What I would like to do is create a reusable stored procedure that pulls all ticketing data that can then be thrown into pivot to sort by season, production season, price type, and genre.  Does anyone have anything they have put together that is close so that I'm not building this from scratch?  They are asking for it tomorrow.  Thanks in advance.

Parents
  • Sorry, no scripts came through.

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brian Wilbur Grundstrom
    Sent: Tuesday, February 14, 2017 2:21 PM
    To: Robert Martin <rmartin@waltonartscenter.org>
    Subject: RE: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    Attached are scripts for the elements needed for the procedure.  I'm not sure all of them are used.  I included our ticket history for example, as I have customed our local ticket history which this references.  Let me know if I have missed anything.  Also attached is the data to set up keywords.  Please note that the resulting data is on the SLI level, so you will need to filter based on what you need.  This gives you move options than ticket history, which is on the lineitem level.  The job can be run with a full reset at night, or an incremental update during the day.

     

    BWG

    From: Robert Martin <bounce-robertmartin8728@tessituranetwork.com>
    Sent: 2/14/2017 6:06:50 PM

    Please share !!

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brandi Sellers
    Sent: Tuesday, February 14, 2017 11:50 AM
    To: Robert Martin <rmartin@waltonartscenter.org>
    Subject: RE: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    I'd love to take a look!  This is exactly what I am looking to create long term.

    From: Brian Wilbur Grundstrom <bounce-brianwilburgrundstrom7163@tessituranetwork.com>
    Sent: 2/14/2017 5:11:04 PM

    I have a routine that runs both overnight and incrementally over the day that creates a local heavily indexed table that many of our ticketing reports run off of, including our customized ticket history display.  Let me know if you are interested.

    BWG

    BRIAN WILBUR GRUNDSTROM | Database Administrator
    SHAKESPEARE THEATRE COMPANY
    Recipient of the 2012 Regional Theatre Tony Award®

    516 Eighth Street, SE | Washington, DC 20003-2834
    p 202.547.3230 ext. 2216 | c 917.952.7957

    bwg@shakespearetheatre.org
    www.shakespearetheatre.org
    www.brianwilbur.com
    2016|2017 SEASON •• Shakespeare’s ROMEO & JULIET • Norman, Simon & Burnett’s THE SECRET GARDEN • Bartlett’s KING CHARLES III • Elevator Repair Service’s THE SELECT (THE SUN ALSO RISES)Shakespeare’s MACBETH • Ives’s THE SCHOOL FOR LIES

     

     

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brandi Sellers
    Sent: Monday, February 13, 2017 3:24 PM
    To: Brian W. Grundstrom
    Subject: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    My Development team is embarking on a campaign to endow our Chamber Music performances.  For background, we are a performing arts festival and our chamber music series consists of eleven separate programs with three performances each.  Here are the criteria they are looking for:

    1. Purchased tickets to at least four performances of Chamber Music at 2016 Festival (Each festival year is season and Chamber Music as a whole is a production season) 
    2. Purchased tickets to Festival at least five years (each year is a season)
    3. Not already listed as a chamber subscriber (constituency)

    We do not utilize subscriptions at this time; it's something I want to work with our Patron Services Manager on for our 2018 Festival.  That is to say all tickets are sold individually.  We don't use packages; there is a price type of Chamber Subscriber for each performance.

    What I would like to do is create a reusable stored procedure that pulls all ticketing data that can then be thrown into pivot to sort by season, production season, price type, and genre.  Does anyone have anything they have put together that is close so that I'm not building this from scratch?  They are asking for it tomorrow.  Thanks in advance.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!

Reply
  • Sorry, no scripts came through.

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brian Wilbur Grundstrom
    Sent: Tuesday, February 14, 2017 2:21 PM
    To: Robert Martin <rmartin@waltonartscenter.org>
    Subject: RE: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    Attached are scripts for the elements needed for the procedure.  I'm not sure all of them are used.  I included our ticket history for example, as I have customed our local ticket history which this references.  Let me know if I have missed anything.  Also attached is the data to set up keywords.  Please note that the resulting data is on the SLI level, so you will need to filter based on what you need.  This gives you move options than ticket history, which is on the lineitem level.  The job can be run with a full reset at night, or an incremental update during the day.

     

    BWG

    From: Robert Martin <bounce-robertmartin8728@tessituranetwork.com>
    Sent: 2/14/2017 6:06:50 PM

    Please share !!

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brandi Sellers
    Sent: Tuesday, February 14, 2017 11:50 AM
    To: Robert Martin <rmartin@waltonartscenter.org>
    Subject: RE: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    I'd love to take a look!  This is exactly what I am looking to create long term.

    From: Brian Wilbur Grundstrom <bounce-brianwilburgrundstrom7163@tessituranetwork.com>
    Sent: 2/14/2017 5:11:04 PM

    I have a routine that runs both overnight and incrementally over the day that creates a local heavily indexed table that many of our ticketing reports run off of, including our customized ticket history display.  Let me know if you are interested.

    BWG

    BRIAN WILBUR GRUNDSTROM | Database Administrator
    SHAKESPEARE THEATRE COMPANY
    Recipient of the 2012 Regional Theatre Tony Award®

    516 Eighth Street, SE | Washington, DC 20003-2834
    p 202.547.3230 ext. 2216 | c 917.952.7957

    bwg@shakespearetheatre.org
    www.shakespearetheatre.org
    www.brianwilbur.com
    2016|2017 SEASON •• Shakespeare’s ROMEO & JULIET • Norman, Simon & Burnett’s THE SECRET GARDEN • Bartlett’s KING CHARLES III • Elevator Repair Service’s THE SELECT (THE SUN ALSO RISES)Shakespeare’s MACBETH • Ives’s THE SCHOOL FOR LIES

     

     

     

    From: Tessitura Shared Reports Forum [mailto:forums-shared.reports@tessituranetwork.com] On Behalf Of Brandi Sellers
    Sent: Monday, February 13, 2017 3:24 PM
    To: Brian W. Grundstrom
    Subject: [Tessitura Shared Reports Forum] Ticketing History for Development Prospects

     

    My Development team is embarking on a campaign to endow our Chamber Music performances.  For background, we are a performing arts festival and our chamber music series consists of eleven separate programs with three performances each.  Here are the criteria they are looking for:

    1. Purchased tickets to at least four performances of Chamber Music at 2016 Festival (Each festival year is season and Chamber Music as a whole is a production season) 
    2. Purchased tickets to Festival at least five years (each year is a season)
    3. Not already listed as a chamber subscriber (constituency)

    We do not utilize subscriptions at this time; it's something I want to work with our Patron Services Manager on for our 2018 Festival.  That is to say all tickets are sold individually.  We don't use packages; there is a price type of Chamber Subscriber for each performance.

    What I would like to do is create a reusable stored procedure that pulls all ticketing data that can then be thrown into pivot to sort by season, production season, price type, and genre.  Does anyone have anything they have put together that is close so that I'm not building this from scratch?  They are asking for it tomorrow.  Thanks in advance.




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!




    This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Shared Reports Forum. You may reply to this message to post to the 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!

Children
No Data