Hi folks,
We are moving from selfhosted to Hosted Services* (aka RAMP). Loads of fun to be had, but it is a sizable project.
If you have run this gauntlet before and have any advice, tips, project workflow magic, I'd love to hear it.
Best,
H
*We're caught in its tractor beam! it's pulling us in!
Congrats, Heath et al on your upcoming moves to Hosted Services!
We made the move to RAMP in 2017. Prior to that we had been self-hosted for 10+ years.
Everyone has already made some great points, and I would echo the sentiment of managing expectations and communication. For example, how hands-on does your DBA want to be in the Tessitura SQL server after the move? As my consortium's DBA it's important for me to know when TN staff apply changes to the system or when the backend jobs that I don't have access to (e.g. Analytics loads) are running, so we definitely have discussed that, and continue to discuss that, with TN.
One of the main things I have asked for since moving to RAMP/Hosted Services was a "handbook", i.e. official documentation on all things Hosted Services, to help with those expectations and communication. Happily there's a (new this year, I think) section in the TN Help system just for Hosting, which is a great start!
Moving to Hosted Services was a great choice for our consortium. There are, of course, trade-offs, but the benefits far outweigh any of those. As the person who by default was responsible for all things tech, the move to Hosted Services let me focus on implementing projects for the consortium, i.e. the job I was hired for, rather than maintaining servers.
Bonne chance!
Thank you. When I was in the THS environment it gave me a lot of time to do more data governance, reports and analysis, and cleaning up workflows across teams. Lots of benefits and still elbows deep in SQL