And in that describe exactly what you do so you can get replaced? I now have a Best Practice for each Sql Server I am overseeing. Well 12 are started, tomorrow we go over DR, BU and possible Recovery from BU.
I have to explain how to set up mail by server type, define spindles in a server setup and backup plans for the server. Disaster recovery plans etc. Current doc is just into seventh page for a single server. This is an easier server because it is only 2000 and not 2005. Do you generally have these documents to do or do you not go this far into it? This is all per customer demand that document what they have and identify what they don't. They had an oh shit moment and brought me in after the customer went rip shit. Since then I have been documenting how to do it properly. It is funny because there is a unique story with each of our clients and how it is done "there." <was that the correct version Ed? > ;-> __Stephen -- Stephen Russell Sr. Production Systems Programmer Web and Windows Development Independent Contractor Memphis TN 901.246-0159 _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[email protected] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
