Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
sumwanlah
Starting Member
43 Posts |
 Posted - 2002-05-30 : 07:04:44
|
| Hey people... Just a thought.Generally SPs are issued and we're encouraged to implement them just to resolve bugs or protect us from encountering these bugs. And occasionally, from list of bug fixes, these contains a few where we can recreate the bugs.Thing is, for those that do not include this helpful guide, how do we know how to recreate these bugs, of course especially those that may potentially affect us?My point is that I'm sure some of us work in an environment where we can't just simply take Microsoft's recommendation literally. Don't get me wrong, I'm not bashing MS... Hahahah!!!I've got to run tests (somehow) to see how existing databases and it's corresponding applications work with the new SP. Only when I 'feel' that things didn't screw up, then I will implement the new SP. Of course, you can't tell when things will blow up in your face!!!I know that the recommendation from MS is that if we feel that we're not affected by any bugs that is fixed in the new SP, then it's not necessary to implement it. Again, how can you be sure that everything's hunky-dory?Kinda like a nice dilemma eh? - You don't implement it? If it's business as usual, the new SP won't bother you. Then again, things may crop up one day when you do something out of the ordinary.- But if you do? Fine, you may be protecting yourself against potential weirdos. BUT! Bugs may STILL appear!What then?------------------------What goes around...? Is the belt around my waist! |
|
|
Page47
Master Smack Fu Yak Hacker
2878 Posts |
Posted - 2002-05-30 : 07:58:50
|
| Just something to chew on . . .My experience has been that its not a question of whether or not I am currently suffering from bugs that are to be fixed by implementing the sp, but what new bugs does this sp introduce into my system.That being said, I think the best thing to do mimic your production environment somewhere isolated and simulate 'a days work' . . . see what happens. If all is well, roll out the sp to dev and see what happens . . .<O> |
 |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2002-05-30 : 08:03:19
|
quote:
I've got to run tests (somehow) to see how existing databases and it's corresponding applications work with the new SP. Only when I 'feel' that things didn't screw up, then I will implement the new SP. Of course, you can't tell when things will blow up in your face!!!
TESTING....TESTING...AND MORE TESTING!I think it helps to be realistic about the kinds of bugs you actually will be victim to. A service pack will fix far more than you will ever experience, it's unreasonable to think you need to worry about all of them or try to guard against all of them. If you did that, you might as well never cross the street for fear of being hit by a car, or leave the house and take a chance of being hit by lightning, or a meteorite, or an airplane falling from the sky...If you don't already do extensive testing during code development, incorporate it into your process going forward. This will help find any bugs that WILL affect you, and you can work around them at the start. If a new service pack fixes the bug, you have the option of rewriting the code or just leaving it; it ain't broke, so why fix it?My personal preference is to always apply the latest service pack, but I'll wait about a month after it's released. If no major new bugs show up in that time, then it will be safe. If that seems too short, then wait 3 months. I've never had anything break by applying the latest service pack. And the bug tracking and workarounds on MSDN are really pretty good, regardless of what you or I think of Microsoft, it could be a lot worse.If you really can't decide, then flip a coin. Just don't sit around worrying about what might go wrong. Either bite the bullet and put the new SP on, or forget about it and get back to work. Edited by - robvolk on 05/30/2002 08:03:58 |
|
|
|
|
|
|
|
|
Evaluating Service Packs