this is to answer the question, "does EVERYONE know sql server?"

[lauralh]

[Poll #433775]

Comments

[verybadlady.livejournal.com]

Somehow I doubt we're talking about the same SQL.

[herbaliser.livejournal.com]

what other kind is there? (http://www.microsoft.com/sql/)

[strukcher.livejournal.com]

DUDE DOES MYSQL COUNT?!?!

[herbaliser.livejournal.com]

technically no, but what the fuck.

[chris.livejournal.com]

i've only used MySQL and a bit of oracle, but hey its all the same sql right?

[verybadlady.livejournal.com]

Um, I use it but I don't write it.

[llarian.livejournal.com]

It goes to 11?

[herbaliser.livejournal.com]

[llarian.livejournal.com]

I assume you mean MS SQL Server, so I'll put 8 with qualification. =)

I'm a rockstar DB2 and Oracle Admin/Developer, but I suck at Sybase/MSSQL still. (MySQL is a joke and I hate using it for anything except quick hacks)

[pootrootbeer.livejournal.com]

I agree with this post.

[herbaliser.livejournal.com]

i think you mean COMMENT

[lisa.livejournal.com]

how is mysql a joke?

please don't say 1. no support for transaction logs or 2. not acid compliant or 3. no support for replication cuz those aren't really valid and haven't been for a long time.

also are you comparing to MSSQL?

[llarian.livejournal.com]

Heh. I figured you might respond to that. =)

Mostly for scalability without running layers over the top of the database like memcached.

And no, I'm not comparing the MSSQL. I don't have enough experience with it.

For large vertical databases (non-clustered, mostly data mine/analysis), which is the environment I've worked the most in, MySQL can't hold a candle to an optimized DB2 or Orcale database. Even with extensive optimization, InnoDB, etc. When I started adding repeated read/write queries on top of larger reads, MySQL fell over completely even with as much optimization as I could wring out of it. I've had no such problems with the others.

(Also, fault tolerance is a biggie. I've had data loss in MySQL before. With DB2, I ran a couple tests where I started a bunch of sequential writes, both large and small units of work, then cycled the power a few times. All work units rolled back the way they were supposed to, and the DB came back up clean every time.)

[lisa.livejournal.com]

when was the last time you worked with innodb?

i just cringe whenever i see people throw around phrases like that. i don't find mysql (with innodb esp) a joke when i see the amount its handling on our site :-D

[llarian.livejournal.com]

Probably a couple years ago? I will admit it was relativly new in MySQL when I ported everything I was doing to DB2 and dumped MySQL as a platform. I couldn't afford the risk at the time, and the performance was a nice benefit.

I totally admit that Livejournal is an amazing application of MySQL, but without massive clustering and memcached, it would fall on its face, no? My experience is that single instances of MySQL can't scale vertically at all, which means you need other layers of stuff on top of it to make it perform well. (Don't get me wrong, BTW, I think memcached is completely badass)

[duckierose.livejournal.com]

I couldn't pick one out of a lineup if al the standins were clones of my uncles.

My lack of knowledge is so absolute, I don't even know what I'm talking about.

[madam0wl.livejournal.com]

I said "7" but I don't know if SQL Server is what I'm rating myself on... I'm just proud that I taught myself little sql queries at work, example:
"select piecename from mk_styles where stylename like '123%blah';"

*sniffle*

[perich.livejournal.com]

It doesn't help.

I still feel bad and stupid.

[herbaliser.livejournal.com]

why, just because I know 5 million database nerds?

Re: *sniffle*

[herbaliser.livejournal.com]

59% !

Re: *sniffle*

[perich.livejournal.com]

Well, that's reassuring.

drishta_ro, who helps hawver manage databases, doesn't know SQL Server either, so that's a relief.

[lemur68.livejournal.com]

I only say 1 instead of 0 because I took a tutorial once.