I'm likely being really naïve here, but the whole 'best practices' thing really turns me off. I can understand if a company doesn't have experienced IT folks and needs something to help them get a complicated device like a server up, running and protected than a BP doc could be really handy. Usually though I see it used more as a weapon than a tool, often by 'outsiders' who don't appreciate the intricacies of what's going on 'inside' in terms of budget constraints, oddball requirements, legacy software requirements and so on. The BP's I've read assume a level of equipment and a willingness to invest in IT infrastructure that is frighteningly out of touch with reality. A BP doc often comes off like a sales pitch instead of useful IT guidance. I'm not saying a BP is a bad thing; I guess I just haven't seen enough of the good ones... Maybe it's just me :)
Dave David Smith Systems Administrator Doan Family of Dealerships (585) 352-6600 ext.1730 [email protected] www.upstatedigitools.com This message may contain confidential and/or proprietary information, and is intended for the person/entity for whom it was originally addressed. Any use by others is strictly prohibited -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Stephen Russell Sent: Wednesday, June 03, 2009 6:15 PM To: [email protected] Subject: [NF] Are you asked to create best practice documents for clients? 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 [excessive quoting removed by server] _______________________________________________ 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/002b01c9e50f$38782d80$a96888...@com ** 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.
