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
Hi Michael!
When I first took over as DBA I had very little Tessitura experience. I highly recommend asking questions as the Tessitura community is the best!
DO NOT underestimate the documentation. Tessitura documentation is some of the best out there and really does cover most things. I tell people all the time I learned everything from the documentation and I still read and reread it nearly every day.
Then learn SQL - I mostly did this with W3 schools (free) and google. It is extraordinarily helpful to understand how things work in the backend so you can add to the front. I recommend having a copy of the Tessitura Table Structures document (under system administration here) on hand so you can start working with the data (in TEST!). The best way to really learn SQL is to do it. Start with checking out the 'show query' tab in list builder.
And also have fun!
I learnt SQL the same way. But it is useful to have a little bit of structured understanding on the database architecture and why things are the way they are. I'd echo that the Tessitura community is invaluable. Maery's links are great.
If TLCC run classes like they have in past years jump into them. SSRS & SQL workshops were amazing for me starting.
Also you'll quickly be amazed at how much little (and big) pieces code you write. Before you build up and unmanageable amount of stuff in a word doc somewhere, get into the habit of saving it into a well referenced git. Also commenting everything you do. Future you will love you for it.
I cannot second Heath's last suggestion more. Prior to getting into git myself, I had what I considered to be an awesome and fabulously constructed series of notepad documents with all my code in all its variations. It made me happy. Then I got into git, and I realized just how easy tracking my code could be. It certainly is great in terms of helping to make sure that you track change over time. Because no matter how good your code is when you implement it, you WILL change it. And this is someone who works HARD to future-proof all of his code. It will be changed, and git is a great way of making sure you track those changes.
And definitely comment. Working on something complex is obvious when you are writing it. While working on and writing a 1,500+ line procedure, you will know exactly what each line is doing inside and out. But come back to that same procedure 9 months later when you need to update it (see the previous paragraph), it will look strange to you. Comment on what you are doing and why you are doing it. No, do not have more comment than code, but a one liner on top of each major query that says "doing this for this reason" goes a long way.
As for the SQL learning, certainly like others have said, your online resources are great. The Tessitura community is fabulous. Google/StackOverflow is always there, too. Never underestimate the value of literally searching the internet for your code problem. And looking at the normally constructed List Manager queries. That was how I got my own start into SQL; there is great value there. As I continue to parrot others, the documentation is useful; learning how the tables interact with each other is essential. Learn the value of (NOLOCK) hints; I almost never run a first time, blind query to investigate an issue without them. But it IS okay to write procedures without them. And of course, if you are going to TLCC... feel free to seek us out. Those who comment here are often at the conference. And we usually like to talk.
Best of luck!
John A. Moskal II
Heath, is your Github public?
(Owing to massive imposter syndrome) Nope. I'd want to categorise for different brains before I do that - like we do for committed Stored Procedure that need to be explained so that when we leave an organisation the new DB Manager (eg: Tom) or Support doesn't breakdown in tears.
Actually when I wrote about that I was thinking of JAM2.0 who inspired me to get busy cleaning up. I think that'd be a great DB Managers Presentation or TLCC Session *hint hint*
But Heath Wilder,
Then I would actually have to prepare something and talk about it. But seriously, always happy to help when I can. I did indeed submit something as a session suggestion for TLCC this year, though I recall that one being more web based. And just officially registered myself yesterday, too.
John A. Moskal II (JAM 2.0)