Main menu
You are here
Adding Performances
Once you have created an event you can create performances to sell tickets to. Click here to learn how to create an event.
Adding a new performance can use a lot of space in the database. Each performance requires about 400-600 bytes. If you create an event with 10 performances, you might require 4K to 6K. Typically, most of the required space is for tickets. Each ticket sold uses between 500 & 1000 bytes, depending on the length of your promotion codes, credit cards, etc.
You can regain the space used, by archiving an event when all performances and reports are completed or at the end of a year.
Festival Seating
Tickets are created at time of sale and a ticket can represent an admission of a number of people (e.g. admit 10). If a ticket always represents one admission, the number of tickets created will be similar to reserved seating.
Example #1
This would require: 600 seats * 30 performances * .6 (capacity) /3 (average tickets qty) = 3600 tickets issued 3600 * 500 bytes = approx. 2 Meg |
Example #2
This would require: 200 seats * 10 performances * 1.1 (capacity) /1 (average tickets qty) = 2200 tickets issued 2200 * 500 bytes = approx. 1 Meg |
Tickets are created at the same time as the performances. One ticket is created for each seat in the theatre so the formula for predicting the amount of space used is relatively constant.
Example
would require: 600 seats * 30 performances = 18000 tickets * 500 bytes = approx. 9 meg |
2 Year Requirement
may require 9 megs * 5 * 2 = 90 megs for 2 years of tickets online. |