Yeah... my favorite is when some guy who doesn't even know what kind of table he's using is trying to use a database.. kinda makes that whole having different types of tables useless.
... because many folks here are talking out their arse (i.e. regurgitating marketing info they've read/heard) and haven't really experienced or tried any of the bs they're shovelling
lol... I don't pretend to understand disk technology down to the electron level but... I feel I can safely say that if you were to say, run a magnet over the surface of one of the disk's platters then any database would have a problem. This is obviously an extreme example but my point is that hardware trumps software. Does anyone know *exactly* what happened physically inside the server when the power went off? (uber h/w geeks please don't waste your time) The correct answer is 'NO'. Therefore to start making generalisations about the robustness of the db s/w used in the server (much less about db software not used in the server) seems presumptuous at best. As for the parent of this message... Sure, you can implement large scale db solutions in MSSQL. Just spend a significant amount of money on the db software. Have some dork who's devoted his life to M$ and has the time/inclination to decipher the inner workings of the bloated, over designed, over complicated, La Brea Tar Pit syndrome 'software' (btw, if u missed a classical computer education try 'The Mythical Man Month' by Frederick Brooks for a thorough description of the problem with 90% of M$ s/w and the clue to my tar pit ref. above) Then even with said dork, something doesn't work right no matter what he tries so he calls in M$ support at $250/hr. 3 weeks later they get it all working and just to end on a positive note, I'll say that it works without a hitch for the next 6 months:-P... and btw, I've used many M$ products extensively, mostly out of necessity(i.e. market or situation driven) so I'm not just talking out of my exit.
The reason we like MySQL in particular (and many other O/S solutions in general) is because generally they are:
1. Free
2. Easy to understand
3. Easy to use
4. Elegant solutions
5. supported by a large group of knowledgable, enthusiastic users
Oh, and my last point about MSSQL... it's always cool if dbs are fast. MySQL -- fast. MSSQL -- not so much. Once again, refer to the book mentioned above...
Slashdot Mirror
Yeah ... my favorite is when some guy who doesn't even know what kind of table he's using is trying to use a database .. kinda makes that whole having different types of tables useless.
... because many folks here are talking out their arse (i.e. regurgitating marketing info they've read/heard) and haven't really experienced or tried any of the bs they're shovelling
lol ... I don't pretend to understand disk technology down to the electron level but ... I feel I can safely say that if you were to say, run a magnet over the surface of one of the disk's platters then any database would have a problem. This is obviously an extreme example but my point is that hardware trumps software. Does anyone know *exactly* what happened physically inside the server when the power went off? (uber h/w geeks please don't waste your time) The correct answer is 'NO'. Therefore to start making generalisations about the robustness of the db s/w used in the server (much less about db software not used in the server) seems presumptuous at best. As for the parent of this message ... Sure, you can implement large scale db solutions in MSSQL. Just spend a significant amount of money on the db software. Have some dork who's devoted his life to M$ and has the time/inclination to decipher the inner workings of the bloated, over designed, over complicated, La Brea Tar Pit syndrome 'software' (btw, if u missed a classical computer education try 'The Mythical Man Month' by Frederick Brooks for a thorough description of the problem with 90% of M$ s/w and the clue to my tar pit ref. above) Then even with said dork, something doesn't work right no matter what he tries so he calls in M$ support at $250/hr. 3 weeks later they get it all working and just to end on a positive note, I'll say that it works without a hitch for the next 6 months :-P ... and btw, I've used many M$ products extensively, mostly out of necessity(i.e. market or situation driven) so I'm not just talking out of my exit.
The reason we like MySQL in particular (and many other O/S solutions in general) is because generally they are:
1. Free
2. Easy to understand
3. Easy to use
4. Elegant solutions
5. supported by a large group of knowledgable, enthusiastic users
Oh, and my last point about MSSQL ... it's always cool if dbs are fast. MySQL -- fast. MSSQL -- not so much. Once again, refer to the book mentioned above ...
ahhh... the cool fresh breeze of a voice of reason ...