Info request for aspiring Systems Admin/DBA/Systems Analyst

Hi everybody!

My name is Daniel Hardegree and I'm currently the Box Office Manager at our organization.  We've been on Tessitura for almost three years and we have a pretty small staff and only a handful of us really use Tessitura beyond just selling tickets.  We've discovered that there is STRONG need for someone who can fulfill more of a comprehensive Systems Admin/DBA/Systems Analyst/General IT role, and I'm looking to move into that position.  I'm in the process  of gathering details to compose a job  proposal to our executive staff and I was hoping some of you guys would be able to point me in the right direction on some of the details.  I'm mostly looking to see what kind  of training and resources one would need for this position.

Here's a little background on myself.  I've been the box office manager for 5 years and am the closest thing to a Tessitura Superuser at our organization.  I ran point on the majority of our implementation process with  oversight from our university's IT project manager and staff.  I am currently in school pursuing a B.S. in Information Systems so I'm already on the path for this kind of role.  I do have some basic SQL skills and understanding but not any practical experience with it.

As mentioned above I really need to discover what all training and resources I would need for this role.  Anything you can provide would be greatly beneficial, and I look forward to your responses.

Thanks!

Parents
  • I guess I will throw my 2 cents in here too. I've been doing this since SQL Server 2000. I have a BS in IT and our configuration is a HA (High Availability) Database that is virtualized on premise. My role is developer/DBA and we are heavily customized here. Although we haven't dabbled in Interceptors yet, we have numerous table triggers that change the data. One of the biggest things we have implemented is a shared folder with sample code that covers the simple to specific things. My memory is not reliable so these code repositories are great when you have to reuse something. 

Reply
  • I guess I will throw my 2 cents in here too. I've been doing this since SQL Server 2000. I have a BS in IT and our configuration is a HA (High Availability) Database that is virtualized on premise. My role is developer/DBA and we are heavily customized here. Although we haven't dabbled in Interceptors yet, we have numerous table triggers that change the data. One of the biggest things we have implemented is a shared folder with sample code that covers the simple to specific things. My memory is not reliable so these code repositories are great when you have to reuse something. 

Children
No Data