Consequences of adding Hotfixes to SQL Server randomly

Use common sense when applying Hotfixes 

So I keep getting this "New updates are availabe" message in Vista and i'm thinking, OK lets go get the update. Easy enough right? I try to download the thing only to find that the version of hotfix that I randomly picked (9.0.3233) won't allow it! Great. It tells me that this "Security Update for SQL Server 2005 Service Pack 2 (KB948109)" won't work with the version of hotfix that I deployed, and I received the dreaded Error(s) found: Code 7342 Windows Update encountered and unknown error message. Now, this is only for my company laptop, so no biggie. But what about the poor soul who just updated 300 SQL Servers with this thing because he or she saw something interesting on the bugfix list, and now they have to revert back to a lower version to install???!!!

My point - don't add any hotfix unless you verify that you are experiencing the exact problem which a particular hotfix addresses. Period, case closed, end of discussion. And for that matter, it might be a good idea to get product support on the phone as well.  (So you don't have to roll back, say, 300 SQL Servers).

-------------------------------------------------------

Don't think you are being slick adding hotfixes, slick.