Ian Massi (12/28/2012)

---

TravisDBA (12/28/2012)

---

Ian Massi (12/28/2012)

---

My goal is to get my coworker trained up to handle more of the admin stuff on SQL Server. He's already a great developer on the platform but having someone available to fill in for me when I'm on vacation or just otherwise occupied will make us a more productive team. We started on this back in November and since I'm taking vacation early in the new year, it should help show us where we need to concentrate.

Heck, just this morning I was going to modify a replication process and then thought, "Hold on, I'll get him to do this when he's back from vacation next week."

While I totally understand your goal, modifying production replication is not what I would start a "trainee" out on, particularly if they have never admin'd SQL Server before. That's a good way to get your production replication screwed up.:-D

Normally I'd agree (especially since a little knowledge can be quite dangerous), but this is a case where "it depends" lands on "it's alright". He'd just be adding some new tables to an existing process that replicates to a development server. No biggie if it falls apart, but I'll be walking him through it and it should be alright. Since the setup is similar to a replication process we have working between 2 production servers, it'd give him some knowledge to at least get started on resolving an issue there if he needs to. Fortunately he's pretty risk-averse so he won't jump into anything he doesn't understand well enough.