SQL Server 2005 Express Beta messes up your SQL Server 2000, BEWARE

  • Thread starter Thread starter ik
  • Start date Start date
Like if BETA breaks so many things, it might as was well be a virus then?

One major difference: you knowingly install a beta, and can choose not to do
so if you're going to be such a crabass about it.

Even with all this whining from you from different aliases, I'd rather have
it this way than not have access to the software at all. Guess you must not
have been around then, when your first test drive of new software was on
release day...
 
So far you have not shown that the beta was designed in a knowingly fashion
to harm your operating system or access and reveal to outside sources your
data (which is what a virus does). All you have demonstrated is that you are
a pre-teen or teenager that found some free (to you at least) software and,
as you did not take even the most rudimentary steps to protect an existing
installation, attempted to install it without following ALL the instructions
and therefore scragged your current installation. You also have demonstrated
you are not a professional and if you work for anyone then I pity them for
the waste of money.
 
To even think that a README and a BETA disclaimer allows you to put
something out that they should have already tested on their owe in
house server shows how out of touch your are with the real world.
Click to expand...

Your poor decision
When you put out a BETA, why not test it on lots and lots other
microsoft computers first. I got these bugs immediately...there are
so many bugs, but to screw up SQL Server 2000 on the same machine,
COME ON?
Click to expand...

Your ignorance

Of course it's on the development machine!! I am not going to
dedicate an entire computer to testing a beta, NITWIT!!!
Click to expand...

Your poor decision
I am also smart enough to NOT put it on production, BUT OF COURSE,
you, MR. MVP, know all about production, RIGHT? WRONG, YOU DON'T
know anything about production because if your are an MVP because you
can't be in two places at the same time and since you spend all you
time answering the same questions over and over again, you can't
actually be doing REAL WORK, nitwit.....
Click to expand...

Your remarkable ignorance

WTH
 
Don't be so arrogant to add the "Information Architect" to your signature.

Whether it wasn't knowing made to harm the system doesn't give Microsoft the
right to offer such crappy and dangerous code to begin with. Just because a
drug is in the last testing stages of clinical trials should allow it kill
someone.

You guys think are so smart, but first look at your own crappy and
unreliable systems before the complete nonsense you spit out.

You call me not a professional, but it's OK to you that one of the last
stage clinical drug trials kills someone as long as it has a disclaimer,
"beta"


The fact you are accepting crappy software for a beta shows the type of
professional you are. Crashing and screwing up other programs on someone
else's system is OK as long as you have the beta disclaimer.

Professionals don't rely on disclaimer labels like "betas" to justify
screwups. They actually make sure it doesn't happen to begin with.

But of course, "Mr. Information Arrogant", you wanted to have some humble
pie today just like some MVP's do all the time here at this newsgroup.

So put down your "Dry Erase" markers from your Ivory Whiteboard and come
down and put your fingers to the keyboard for once and code something on
your computer that totally needs to be reformatted because it has a beta
that damages your computer like a virus does.
 
WRONG, poor decision by Microsoft to put out BETA when it's really ALPHA.

Now, beta users will spend a lot of their time fixing their computer instead
of testing the beta.

See the difference?

Now, what were you saying?
 
showme said:
WRONG, poor decision by Microsoft to put out BETA when it's really
ALPHA.

Now, beta users will spend a lot of their time fixing their computer
instead of testing the beta.

See the difference?

Now, what were you saying?
Click to expand...

Not true. You'll notice that the OP's ridiculous comments appear to stand
out from nearly all the others. Whether that is from the Beta or from
his/her own carelessness we will never actually know; however, some things
can immediately be attributed to poor decision making from the OP:
(1)Installing a beta product on a development machine which is in turn
dependent upon that product (I assiduously avoid this.) (2)Assuming that a
Beta product won't have installation bugs. (3)Assuming that the Microsoft
SQL Server team has unlimited machine configurations and time to test upon
(hmmm, why would they bother with a Beta then?) (4)Assuming that an SQL MVP
in this ng would not know anything about a production environment, lol.

Basically a whole lot of ASSuming being done by the OP. Can you hear what
I'm saying?

WTH
 
WTH said:
Not true. You'll notice that the OP's ridiculous comments appear to stand
out from nearly all the others. ...
Click to expand...

Just so there's no confusion, "ik" and "showme" are the same person. I am
glad to see he/she/they have some company, because it was getting pretty
lonely on that side of the argument.
 
Chris Hohmann said:
Just so there's no confusion, "ik" and "showme" are the same person.
I am glad to see he/she/they have some company, because it was
getting pretty lonely on that side of the argument.
Click to expand...

I noticed, I was just waiting for showme to say something like "ik said..."
and then eviscerate him/her.

WTH
 
professional you are. Crashing and screwing up other programs on someone
else's system is OK as long as you have the beta disclaimer.
Click to expand...

Uh, we choose to download and install beta software on our own machines.
Who made anyone else "crash and screw up" their systems?

Once again, this trash you're spewing is laughable... it's BETA, download AT
YOUR OWN RISK. Any professional knows that. If you screwed up your system,
don't point fingers at us or at Microsoft. You did it willingly.

A
 
WRONG, poor decision by Microsoft to put out BETA when it's really ALPHA.

WRONG, poor decision by you to install a beta (or an "alpha") on a
production machine.

It is certainly not an alpha release. I have been running numerous builds
on several machines and have not had any problems.

Tell us, honestly, if it said "Alpha" you wouldn't have downloaded it? Give
me a break.

A
 
I think there is a valid point in there somewhere aside from all the horse
manure which needs to be considered. The sql server needs more work. It
wouldn't install on my system, and then it wouldn't uninstall. It took down
my vs2003 as well resulting in days of re-installing etc. I don't really
care to point fingers either, my point is that 2005 needs a bit more
tweaking.
 
manure which needs to be considered. The sql server needs more work.

--
http://www.aspfaq.com/
(Reverse address to reply.)



It
wouldn't install on my system, and then it wouldn't uninstall. It took
down my vs2003 as well resulting in days of re-installing etc. I don't
really care to point fingers either, my point is that 2005 needs a bit
more tweaking.

--
Regards,
Alvin Bruney
[ASP.NET MVP http://mvp.support.microsoft.com/default.aspx]
Got tidbits? Get it here... http://tinyurl.com/27cok
Aaron said:
WRONG, poor decision by you to install a beta (or an "alpha") on a
production machine.

It is certainly not an alpha release. I have been running numerous
builds on several machines and have not had any problems.

Tell us, honestly, if it said "Alpha" you wouldn't have downloaded it?
Give me a break.

A
Click to expand...
Click to expand...
 
manure which needs to be considered. The sql server needs more work.

Yep, that's why it's called a beta.
It took down my vs2003 as well resulting in days of re-installing etc.
Click to expand...

It's a beta. It should have been installed on a throw-away machine, or
partition, or within virtual pc / vmware etc. I believe there are known
issues about installing it alongside versions of .NET 1.1... but in any
case, it shouldn't have been installed where "resulting in days of
re-installing" would be an issue.

It's a beta.

It's a beta.

It's a beta.
 
no complaints. it's my fault. i wasn't pointing a finger.

but you have to admit that its been a while - in my estimation at least -
since a beta went south like that. I would have expected an alpha to skip
town, but i was dissappointed in the beta behavior. disappointed because a
beta is potentially a release candidate. major issues should have been
sorted out. minor issues should still need tweaking. a beta taking a dump on
a computer needs a lot more than minor work based on the release time frame
microsoft has.
 
but you have to admit that its been a while - in my estimation at least -
since a beta went south like that.
Click to expand...

I, on the other hand, have had absolutely no problems, nor have my
colleagues that are beta testing. So what "went south" for you might be
more of an exception than the rule (or maybe something to do with mismatched
..NET versions I mentioned earlier, which I thought was a documented issue!).
beta is potentially a release candidate.
Click to expand...

No, it isn't. Which is why it isn't called a release candidate. In server
products like this (Windows, SQL Server, Exchange), RCs are not labeled as
such until long after beta 3. SQL Server isn't even at beta 2 yet.

SQL Server Express was a technical preview, not a release candidate. Why
did you (or should anybody) treat this with any less scrutiny than any other
beta product? B-E-T-A. Beta, right.
major issues should have been sorted out.
Click to expand...

A beta is designed to sort out major issues. If all the issues are already
sorted out, we'd have a final release!!! Maybe instead of complaining that
"Microsoft f***ed my system", ik and showme can get together and file an
actual bug report and help sort this issue out.
a beta taking a dump on a computer
Click to expand...

ONCE AGAIN! *YOU* choose the computer to install a beta on! And once
again, why is this beta suddenly expected to be so much more omnipotent and
flawless than any other beta product? I think your expectations are a
little ridiculous.
needs a lot more than minor work based on the release time frame microsoft
has.
Click to expand...

Are you sure you're aware of the release time frame??? It's a YEAR away!
So, don't install it if you're not willing to deal with product maturity
issues.

Repeat after me: it's a beta! I will not install it on a machine I rely on!
Why? Because it's a beta! It is not a final release!

I can only hope that sniveling like that in this thread does not lead to
Microsoft closing the door on programs like this, and not letting you see it
until the day it's released... for the benefit of the few people who
knowingly grab and install a beta on production machines and shoot
themselves in the foot, and do nothing but gripe about it...

Microsoft is damned if they do (aw, look what you did to my machine, big bad
M$!), damned if they don't (aw, come on M$, let me play with it!).

It's really too bad.

A
 
You are missing the entire point. The whole point of the thread is that this
is not the exception. rather than dismissing OP and name calling because
this was posted by you
NITWIT!!!
Click to expand...

you should listen to the main point which is the sql edition has major
problems. These problems are show stoppers. I believe that was the giest of
OP's comments. Hiding behind beta technicality does not fix the problem that
it is an issue. if it isn't resolved, the software will miss its ship date.
how does MS know if there are major issues? they rely on the beta pool of
testers to inform them. but you are dismissive of OP which is counter
productive and it also discourages other users from installing the beta.

And yes, i did submit a bug report. And yes my computer is open to allow MS
to gather detailed information. The point of a public beta is to gather
feedback and to see what works and what needs work. i would hope that
microsoft has the sense to weed thru the feedback both positive and negative
to find the real issues plaguing the users because it is valuable. 3.5
million people tested vs02. They didn't all have secondary machines which is
why .net was the largest public beta ever from MS. Some people like me take
the chance and install it on their main machine. the beta only releases
microsoft from liability. i wasn't blaming microsoft for trashing my system.
i was saying that the beta NEEDS work. If you can't understand the
difference, i've wasted my time.
 
rather than dismissing OP and name calling because
this was posted by you
Click to expand...

No, it was not. I suggest you review the thread again, and pay close
attention to matching the From: column to the text of the message. Please
point me to a post where I've used the word nitwit (other than this one, of
course).
you should listen to the main point which is the sql edition has major
problems.
Click to expand...

Yes, it does. It is also a beta product, so it is *expected* to have
issues.
These problems are show stoppers.
Click to expand...

Maybe in your case, but not for the majority. XP has show stoppers too,
again not for the majority. Should it not have been released either? With
the scope of Microsoft products, do you think it's even marginally
reasonable to expect any single server product to have 100% successful
installation success, prior to BETA 2??? Again, you're being completely
unreasonable.
how does MS know if there are major issues? they rely on the beta pool of
testers to inform them. but you are dismissive of OP which is counter
productive and it also discourages other users from installing the beta.
Click to expand...

I dismissed the OP because he said, essentially, "Microsoft sucks because
they ruined my production machine." Had he given some actual substance in
his post, instead of acting like a grade school child stamping his feet
because he spilled beans on his knickers, I might have given a little more
attention.
 
I am not so arrogant to add "Information Architect" to my signature. That is
my job title here. As I am assuming yours is "Senior at <enter appropriate
High School name here>". I have worked my way up through the ranks fro
programmer to systems engineer to this position. I have not forgotten
everything I learned either from school or life's experience. When I
download SQL Server Yukon Beta 2 I will take care to install it on a machine
that I can restore at will without impacting other users. That is a fact of
life.

Do you program? have you ever tried to build even the simplest accounting
package? it is difficult to get what you view is right to even work on your
own equipment let alone a clients. And then there is the issue of what you
think is right and what your client thinks is right.
 
As I am assuming yours is "Senior at <enter appropriate
High School name here>".
Click to expand...

Far too much credit and respect. I would have guessed freshman at high
school or senior at middle school.

A
 
Back
Top