Look Its 2008, You Are Responsible For What You Install On Your Oracle/SQL Server Database


I just saw an interesting article on CNET News.com posted by Tom Krazit Titled “Think before you install”.  The opening line is..

 “Look, people, it’s 2008: You’re responsible for what you install on your PC.” God I wish I had thought of the tag line it’s 2008: You’re responsible for what you install on your PC. With that said lets use it to our advantage. My variation on this tag line would be:

It’s 2008: You’re responsible for what you install on your Oracle Database.

It’s 2008: You’re responsible for what you install on your Microsoft SQL Server Database.

Before I go more into the article that started me on this train of thought about how you are responsible for what you install on your Oracle or Microsoft SQL Server database, lets talk about it.

Just because a vendor ships you an update or patch does not mean you need to install it. Think before you install. Some Vendors are better than others. But ultimately you are running your business on the database. Every time you introduce new software to the Oracle or Microsoft SQl Server database, there is an element of risk. Make sure you read the fine print on the patch. Make sure you have done your homework. Make sure you actually need the patch.

Over the past few years I have had to get involved with a few clients that wanted us to apply a patch straight to production.

 Oracle sent the patch, its Oracle of course we should just apply the patch. straight to production.

The DBA LAW #1. Never Install a Patch Straight onto a production Database. Always test it in Development or Test first. 

We have had to put the breaks on with these clients. We had to protect them from themselves. If we are going to apply the database patch, lets do it properly.

Step 1. Research the Patch.

This means read the fine print. Read the release notes. Perhaps check in with you local Oracle or Microsoft SQL Server users group. Perhaps do an old fashion Google search.

Step 2. Decide if you need the database patch

Do you need this patch? Does it fix a problem you are having or might experience? Is it relevant for your environment?

Step 3. How Critical is this database patch

If the answer is you need this patch. How critical is it?. Is it a security patch? One you understand how critical the database patch is, you can determine how fast you need the patch.

Step 4. Apply the Database Patch to Test/Development First

What a novel idea. Put it in an environment where you can make sure the database patch actually works. Test it, Test it & Test it

Step 5. Back up your production Oracle or SQL Server Database before You apply to your production database.

The Morale of this Story. Vendors release software before its ready.

It’s 2008: You’re responsible for what you install on your Oracle Database.

It’s 2008: You’re responsible for what you install on your Microsoft SQL Server Database.

No back to how I was inspired to write this blog entry. I saw an article titled “Think before you install” Posted by Tom Krazit on C/net News.com. It’s about the latest bonehead maneuver from a software vendor. In this case its apple computer. To quote to article

“The outrage is spewing forth over Apple’s move to include Safari 3.1 as part of its Software Update program. The new twist is that Windows users who never had installed Safari are now seeing it pop up in Software Update, where they are accustomed to seeing updates for iTunes and Quicktime, and that’s not sitting well with many who inadvertently installed the browser.”

I don’t know why vendors insist on doing things like this. But as they say buyer beware. Or in this case Installer beware.  The article goes on to say

“Short attention span syndrome strikes again. This practice, of trying to get people to install your software through coy tactics, has been going on for years. All the major IM vendors have tried it at one point or another. Yahoo faced an outrage in 2005 over the fact that its “standard” installation of a Yahoo Instant Messenger application included toolbars and this really obnoxious “live words” thing that directed people to Yahoo Search.”

The point it’s your PC. Be careful what you install on it. How many times have I had to rebuild my kids PC’s because they became infiltrated with software that brought the machine to its knees. I don’t even try to rescue the PC anymore. I just Initialize the hard drive and start over.

These vendors count on you being condition to just install whatever comes from an official source. To read the entire article click here

The Morale of my Story. Vendors release software before its ready.

It’s 2008: You’re responsible for what you install on your Oracle Database.

It’s 2008: You’re responsible for what you install on your Microsoft SQL Server Database.

Posted Michael Corey, Ntirety

www.ntirety.com

 

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.