Hello Everyone! I am the Database Manager for the Rochester Philharmonic in Western NY. I never saw myself on the digital side of things, so I wanted to start a discussion where some of the veteran Database Managers, or people with a good deal of experience, could share some of the Lessons/advice/dashboards/etc. they find to be essential, unique or otherwise important to their work. I'm sure I am not the only person who would benefit from this, but as a 25 y/o who is 3 months into this position, I would love to learn more and get these gears spinning! Thanks all, I look forward to contributing here however I can. Michael
I had no background in database management or CS when I started and I read a few books on SQL and the one I learned best from was SQL for Dummies.
Also, a lot of the tasks of the job are things you only do once a year, so I recommend starting a document that is a timeline of what you are doing in each month so that you can get ahead of it next year. Did you just learn that your website breaks when the source code date expires at the end of the fiscal year? Put it in the document!
I'm attaching my version of this which is very specific to me and my organization but might give you some insights.Annual To-Do Timeline for Tessitura Operations 10.23.20.pdf
Thank you for the timeline, Kanani! This is a great template to build off of.
I don't think this is necessarily common knowledge, so I wanted to let everyone know that you can now (as of version, I have no idea) have a comma delimited list of default source codes in that t_defaults field. This wasn't always the case, so I wanted to share since you brought the source codes up. Super nice to have since you can schedule a new one to be active when the old one expires, right at midnight. I want to also agree that a list like yours is very helpful.
Thanks, Ryan! I think I learned that at our last FY changeover and had forgotten about it. Also, Tessitura now sends us messages when the source code is about to expire. Maybe because we are on RAMP, IDK. Anyway, I like to use that as the prime rude awakening example of my early DBA days that were trial by fire.
I too had a traumatizing experience with the default source code. Fun times!
Ryan Rowell said:I too had a traumatizing experience with the default source code. Fun times!
Haven't we all? Blessings to whomever added support for a comma delimited list in the 'Default Source_no' field in T_DEFAULTS. ;-)
@Ryan Rowell . Is there documentation on the comma delimited list for the default source codes in T_Defaults?
Yes, when in the System Table, in the bottom right corner, click Table Help.
Tessitura v15 Help System - System Defaults Table (tessituranetwork.com)
The ID of the source to use for web orders. If the source entered here is inactivated, such as when the season ends and all appeals for that season are closed, constituents will not be able to complete ticket orders. A comma-delimited list of sources can be entered in order to prepare for the end of season/year changes from one source to another. The source for a web order can be changed at any point prior to checkout. This entry is required for the Web API.
As of v15.1.14, a notification will be displayed at log in for users in Administrator user groups if a Default Source_No entry has a source expiring within the next 15 days without another source that starts immediately after it in the comma-delimited list. The notification includes the expiring source(s) for reference.
Neil