Here are my 2 cents about this topic... (will probably be more than a buck's worth though :-) )
First never trust anyone's documentation. We are all human, and unless 100% automated, mistakes will be made! Always have a DEV->TEST->PROD process. I know of the additional costs, but for safety and isolation reasons it makes sense... What is even BEST PRACTICE is you have a SANDBOX && DEV - by this we have a short process: 1. Same Code-Base (binaries) on each server - since we are using VMWare a clone is quite easy and quick :-) 2. Clone (copy) the database from SQL X --> Y 3. Install any "unknown stuff" (BMC Patches, Demo Packages, etc) into the SANDBOX! 4. Get the magnifying glass and start "looking"... OK, now to "applying fixes"... Ensure that only one person is on the system in Admin at the time of the update. Enable ALL SERVER EVENT LOGGING (rant - will not catch Import arx files need additional file-logging for that...) Install the patch/update Export all Server Event Logging Entries to a safe-store (Excel/access/ what ever you like) Use this as the "Reference" of what changed, and then you can take the time to compare back to the documentation. We do this (or try at least) during big updates when the code is put into TEST. IF (okay when) we see a Filter/AL/xx in the list of updates, but not the documentation, we go back to the responsible developer and give them a kind-reminder to check their documentation :-) - Sometimes the negative is also the case, something is in the migration specifications, but not contained in the packages :-( At this point we can "copy back XX from production" or leave in the migration and update the documentation. As much as you try to remove Human Factor from the process, Humans are always involved... HTH Thanks-n-advance; HDT Platform Incident / Problem Manager & Architect Robert Molenda IT OS PA Tel: +1 408 503 2701 Fax: +1 408 503 2912 Mobile: +1 408 472 8097 [EMAIL PROTECTED] Quality begins with your actions. ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kathy Morris Sent: Wednesday, August 22, 2007 9:07 AM To: [email protected] Subject: Re: Production To prevent this from happening - can we identify all the objects and dependencies and backup the data associated with those objects - scrub the data and reimport into the form? ________________________________ Get a sneak peek of the all-new AOL.com <http://discover.aol.com/memed/aolcom30tour/?ncid=AOLAOF00020000000982> . __20060125_______________________This posting was submitted with HTML in it___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
