December 26, 2008 at 7:08 pm
Comments posted to this topic are about the item How Would You Rate This? - Database Weekly (Dec 29, 2008)
December 31, 2008 at 1:31 pm
Since the vulnerability is fixed in SP 3 for SQL 2005, and since that's available now, I don't know that I'd panic about this one. It is a long time to leave it unfixed, but I hate to second-guess people on that kind of thing.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
December 31, 2008 at 3:35 pm
Heh... well, what's the matter? Didn't they follow the "time to market" and the "splash for the cash" paradigm that everyone seems to preach... instead of writing quality code that shares a concern for the customer at large?
They just did what I've been preaching against and that most of you (sorry Steve, you're included) seem to embrace when your ill-informed boss says "meet the schedule or die". No hair...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2008 at 4:08 pm
I do think they ought to adhere to a schedule, but not at the expense of bad code. And this is a management issue, not a coder issue. I think MS as a whole is making a mistake here, not getting patches out.
January 1, 2009 at 12:18 pm
Steve Jones - Editor (12/31/2008)
I do think they ought to adhere to a schedule, but not at the expense of bad code.
[font="Arial Black"]FINALLY![/font] That's exactly what I've been saying for the last 30 years!
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2009 at 12:21 pm
Glad we agree on something 🙂
Happy New Year
January 1, 2009 at 12:37 pm
Heh... Happy New Year to you and your's, Steve!
Man... keep up the awesome work on SSC... I went a visited more than a dozen other sites just to see "what up", and they just don't hold a candle to what you've done on SSC. Some of the sites haven't had a question asked or answered since Sep 2008 or before.
--Jeff Moden
Change is inevitable... Change for the better is not.
January 9, 2009 at 8:03 am
The biggest problem, in my opinion, with Microsoft, (and probably a fair number of other large companies), is a lack of openness and information about important things that us users want to know.
What they should've said, is that they're planning an update but it's been delayed and then provided a reasonable explanation.
After all, when someone tells you that something they're working on, is taking longer than expected because of *something*, your response will almost certainly be along the lines of "ok, let me know when you've finished", instead of tearing them apart for the delay.
January 10, 2009 at 11:13 am
Paul, I tend to agree with that. MS is open in some ways, but very closed in others.
Let us know there's something in the works. In this case, I'm not sure why a workaround wasn't disclosed in April. Information would help slow down the ping ponging people get from getting too upset about a lack of information and then upset about too much information.
Some of that won't go away as people like to complain. And reporters need something to write about.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply