Hello!Our Tessitura/IT Manager recently retired after 17 years, and I'm looking for any and all advice you might have on managing that transition. We're on RAMP, so much of our regular maintenance is covered, but I'm worried about all those little things that fall through the cracks. People who have been through this before -- help!
Thank you!
A couple of quick suggestions: - Do an audit of all your SQL Server scheduled jobs (ask for help from the Hosting Services team if necessary) to find jobs created by that admin. When you've had a database admin in place for a long time, it's nearly always a revelation to discover what they had running as automations. - Run a search in SQL Server for all objects in the database owned by the userid of the user who's leaving. Here's a handy reference to a script that does just that. https://dba.stackexchange.com/questions/33551/can-i-retrieve-all-database-objects-owned-by-a-particular-user. You won't immediately, and may not ever, need to alter any of these objects, but knowing what they did create will be very helpful later if custom reports or procedures need to be altered. - Similarly, check for any scheduled reports that belong to that user and plan for who they should be owned by now. Fortunately, version 15 makes this very easy in the updated reports management interface. - And the most basic but perhaps the most overlooked - remember to remove that user's user group access and inactivate their login. Hope all this helps!
Jonathan
You also might want to check in with some of your super users or members of management to see if there were any special reports the IT Manager used to run for them on a regular but infrequent schedule - that report that only needs to go to Development once a year or the special ticketing update that happens every 6 months or for specific types of on sales - the things you tend to forget about when thinking about your regular duties.BestJess LevySan Francisco Opera
Of course, having worked with you, they would be a fine, upstanding member of the community and commented all their code. However when you kiboze the database for their objects (and before they get too far away for favours), have a quick look at their views and sprocs and make sure that they are adequately commented. Might save you a lot of hassle later. A list of all local objects and what they are intended for is a good idea anyway.