You Shouldn't Have Done That

Question

You Shouldn't Have Done That

Steve Jones - SSC Editor

SSC Guru

Points: 734522
More actions
August 31, 2009 at 9:38 pm

#214475

Comments posted to this topic are about the item You Shouldn't Have Done That

Viewing 15 posts - 1 through 15 (of 35 total)

You must be logged in to reply to this topic. Login to reply

Elliott Whitlow SSC Guru Points: 102402 More actions · Answer 1

So in other words, be nice, even if the answer is that was a really stupid thing to do? Over the years I've inherited many peoples great ideas and had to make them work and rarely could I ask (out loud) who is the idiot who built this thing? And I'm sure someone could ask that about some of my really early work..

I just wish that people would do a search of the forum or a google search before asking a question here.. And then they could ask a question that is more closely tied to their problem.. Also maybe get an idea of what information they need to post..

CEWII

IceDread SSCertifiable Points: 5050 More actions · Answer 2

I recently installed sql server 2005 on one of my computers with win vista, I installed everything there was to install and patches etc and it of course worked great. Then a couple of years later, one month ago, I wanted to remove sql server 2005 from that computer and I did get to remove a few parts and then suddenly I could not remove sql server 2005. Some of the parts could not be found but some parts of sql server would anyway start up on restart. It just didnt work to remove them by the control panel. So that's my warning to you all, before you remove sql server, search a bit first on how that best is done, instead of like me, just starting to remove each thing listed in the control panel that I wanted removed since sql server was just not a single item in that list as you may know. It really was annoying.

PostXript Right there with Babe Points: 719 More actions · Answer 3

Oops... that closing sentence hurts... glad I'm not the only person who ever did that 😉

Ross McMicken SSCarpal Tunnel Points: 4395 More actions · Answer 4

PostXript (9/1/2009)
Oops... that closing sentence hurts... glad I'm not the only person who ever did that 😉

That's a major reason we don't allow scripts to be run against production unless the results have been tested by the end users in an acceptance system. Even simple Update table set flag = 1 require a change management documetn in our environment. To make it even more difficult to induce errors, the DBA's that execute the scripts have nothing to do with creating the scripts.

PostXript Right there with Babe Points: 719 More actions · Answer 5

I totally agree, this was a few years back. In my current environment it's no longer possible for me to make these kind of mistakes.

Ross McMicken (9/1/2009)
PostXript (9/1/2009)
Oops... that closing sentence hurts... glad I'm not the only person who ever did that 😉
That's a major reason we don't allow scripts to be run against production unless the results have been tested by the end users in an acceptance system. Even simple Update table set flag = 1 require a change management documetn in our environment. To make it even more difficult to induce errors, the DBA's that execute the scripts have nothing to do with creating the scripts.

george sibbald SSC Guru Points: 104210 More actions · Answer 6

Note 2 in the following URL would suggest that you can upgrade from evaluation edition to enterprise (or any other)

http://msdn.microsoft.com/en-us/library/ms143393(SQL.90).aspx.

I suspect this becomes untrue once service packs have been applied? If someone attempts to upgrade and it does not work the real error would be with microsoft documentation in not making it crystal clear (in one place) what you can and cannot do.

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

Ross McMicken SSCarpal Tunnel Points: 4395 More actions · Answer 7

PostXript (9/1/2009)
I totally agree, this was a few years back. In my current environment it's no longer possible for me to make these kind of mistakes.
Ross McMicken (9/1/2009)
PostXript (9/1/2009)
Oops... that closing sentence hurts... glad I'm not the only person who ever did that 😉
That's a major reason we don't allow scripts to be run against production unless the results have been tested by the end users in an acceptance system. Even simple Update table set flag = 1 require a change management documetn in our environment. To make it even more difficult to induce errors, the DBA's that execute the scripts have nothing to do with creating the scripts.

I forgot to mention that the folks who CAN make changes in production have to log in using a special ID that doesn't do any routine activites like email and has no authority in test or ddevelopment. That prevents the big oops that happens when you use an ID in the wrong environment. "Gee, I thought I was in test, not production"

Mike Stuart Right there with Babe Points: 760 More actions · Answer 8

Back to the original statement of "... you shouldn't have installed all that for an evaluation edition" - why not? Isn't that why we have evaluation editions: to see if they work, or not, with various components? Yeah, I know that this isn't necessarily the direction this blog is going, but it makes sense to me to install evaluation editions of not only SQL Server but 3rd party vendor / in-house developer software and see how it plays out against the existing parts and pieces of the environment.

blandry SSCarpal Tunnel Points: 4821 More actions · Answer 9

I agree that this kind of comment - "you shouldn't have done that" - is totally counter-productive, but I also think Microsoft does a regularly lousy job with releases, updates, and installs.

We have dealt a great deal with clients who installed SQL Express and then tried to move to full versions, and had bizarre problems. We've also had our share of support calls over clients changing SQL versions. When you go to the web to find documents to help you out, without exception, the worst instructions come from Microsoft themselves who seem hell-bent on always, always, always over-complicating such "help". One of our clients tried to follow an MS document that suggested tweaking the registry and that was a three day support call!

Case in point, Microsoft's recent release of Visual Studio 2008 hoses up Winzip. They released an SP1 update which not only DID NOT fix this problem, it added a new problem causing Windows Media Player to lock up. Microsoft has "acknowledged" the problem, but has said nothing about a fix, and worse, is behaving like this is somehow 'okay'. (Anyone experiencing these problems can go to the MSDN forums where some "phixes" are presented by end-users - they are not pretty, but work for the most part).

Yes, we all make mistakes, I agree - but when the company building the software makes a mistake there has to be something more than just an 'acknowledgement' of the problem and the attendant months-long wait for the real fix. It strikes me that if I took my car into the dealer and he screwed up my car worse than when I brought it in, it would not be acceptable for them to tell me my car would be fixed in some nebulous amount of months.

In short, I sure would love to tell Microsoft; "You shouldn't have done that!!!"

There's no such thing as dumb questions, only poorly thought-out answers...

IceDread SSCertifiable Points: 5050 More actions · Answer 10

blandry (9/1/2009)
Case in point, Microsoft's recent release of Visual Studio 2008 hoses up Winzip. They released an SP1 update which not only DID NOT fix this problem, it added a new problem causing Windows Media Player to lock up. Microsoft has "acknowledged" the problem, but has said nothing about a fix, and worse, is behaving like this is somehow 'okay'. (Anyone experiencing these problems can go to the MSDN forums where some "phixes" are presented by end-users - they are not pretty, but work for the most part).
Yes, we all make mistakes, I agree - but when the company building the software makes a mistake there has to be something more than just an 'acknowledgement' of the problem and the attendant months-long wait for the real fix. It strikes me that if I took my car into the dealer and he screwed up my car worse than when I brought it in, it would not be acceptable for them to tell me my car would be fixed in some nebulous amount of months.
In short, I sure would love to tell Microsoft; "You shouldn't have done that!!!"

At least they do acknowledgement, thou they should have fixed it asap. However, there are several companies out there that does not acknowledge problems with their products and ban people from their forums if they talk about specific issues/ bugs. All thou if MS were to do that there would have been an outrage and perhaps even probably lawsuits.

BJ Hermsen Hall of Fame Points: 3123 More actions · Answer 11

I think that one of the bigger issues we face as more and more people embrace the virtual realm(s) is that we hide behind the screen. We do not have to accept onus for our comments. In the same token we often do not do all of the research we should prior to posting questions. I have done both myself and I always kick myself for it. Anyone who thinks they don't make mistakes or that they catch all of them on their second go is making a major mistake. We never finish learning and likewise we should also never finish teaching. There is always something we could improve upon for ourselves and what good is that knowledge without sharing. It sure does not mean job security like some people feel.

Gail Shaw SSC Guru Points: 1004504 More actions · Answer 12

Mike Stuart (9/1/2009)
Back to the original statement of "... you shouldn't have installed all that for an evaluation edition" - why not? Isn't that why we have evaluation editions: to see if they work, or not, with various components?

There's a difference, in my opinion, between installing for evaluation and installing on a production server and using as if it was a fully licenced and permanent version.

Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

ewan-978102 Newbie Points: 9 More actions · Answer 13

Frankly, this is a problem that MSFT should own. We live in a world that disproportionately rewards small differences, and software installation is no different. The less time you waste on trivial and inconsequential issues like upgrading from eval to full, the more time you have to focus on adding value. Last time I looked, that is our prime directive.

GSquared SSC Guru Points: 260824 More actions · Answer 14

I once licked a live electrical cord to find out if it was plugged in. Thus, I'm not in a position to criticize ANYONE for "you shouldn't have done that" type issues. Doesn't mean I don't occassionally do it, but it does mean I shouldn't and usually don't.

- 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