RE: Re[2]: MySQL vs Microsoft SQL
James, Gotta say that this is a bad reason to choose one product vs. another... because it lacks a GUI to build queries? Undertanding SQL is all well and good, but I can tell you that I would give anything to have a query builder that works like the one for MS SQL server. You may enjoy writing incredibly long join queries because it demonstrates your understanding of SQL syntax. Personally, I'd rather spend my time watching grass grow. What is the value of doing something in code which is inherently visual, and is a lot easier to do visually? You do make a valid point, part of the reason I like M$SQL is that you can build complex expressions with their GUI tools, but Last year, I did some work for a client and he requested that I do it in-house. Now, since I was on a deadline (2 weeks), I figured I'd use the Enterprise Manager to build my stuff and off and away I go. Well, for some strange reason I was never able to determine why, but it took 15-20 minutes to connect to a database on the East Coast. When I attempted to connect via the query analyzer, the connection was instantaneous. I learned by visual means to create tables, add triggers, yada, yada, yada... Well, this was definitely a learning experience because now I had to learn how to do everything by DML via the query analyzer if I was going to meet this deadline. Now I prefer to do all my work using a command-line tool. I recently upgraded to SQL2000 on my machine at home and have encountered the same situation again! Fortunately, I can drop out of GUI-mode and work by DML until I can figure how why this happens. I understand that every user has a right to choose how they want to work, but I often see colleauges using a GUI tool to change a datatype or some other menial task (often with several mouse clicks and waiting for the GUI tool to open up) which can cause one to lose more productivity when more often than not, to do it one simple command from a production standpoint makes no sense to me. A query builder will not make a database developer out of a novice, but it can make a professional developer's job a lot easier. True. I can spend my time writing complex code that can't be done with a tool, and not waste it doing repetitive, boring joins that take a few seconds with a visual tool. That's where I do agree with you, and one of the things I don't like about M$SQL. To a certain degree, wizards are nice, but when it lulls a user into a false sense of security about being able to build queries quickly, what do you do when it doesn't become available? It's like a cashier saying to you that they can't give you change, because they don't know how to do it without a machine??!! (Don't laugh, I've had that happen to me on many occassions) Sorry to make this so long My $0.02 Christopher Oson - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re[2]: MySQL vs Microsoft SQL
Gotta say that this is a bad reason to choose one product vs. another... because it lacks a GUI to build queries? Undertanding SQL is all well and good, but I can tell you that I would give anything to have a query builder that works like the one for MS SQL server. You may enjoy writing incredibly long join queries because it demonstrates your understanding of SQL syntax. Personally, I'd rather spend my time watching grass grow. What is the value of doing something in code which is inherently visual, and is a lot easier to do visually? A query builder will not make a database developer out of a novice, but it can make a professional developer's job a lot easier. I can spend my time writing complex code that can't be done with a tool, and not waste it doing repetitive, boring joins that take a few seconds with a visual tool. I am not arguing for MS SQL Server vs. SQL server, I just think having tools is better than not having them. You would always be free to write your MS SQL Server code by hand... Here's looking forward to the future Mascon release that includes a query builder... Jamie At Friday, March 23, 2001 on 6:58:26 PM, you wrote: Not only that, but mySQL "forces" you to learn SQL. Not by wizards that build the SQL statement for you. Like J. Zawodny says, if it meets your needs, then do it. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
MySQL vs Microsoft SQL
*This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. Thanks, Ciprian A. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL vs Microsoft SQL
On Fri, Mar 23, 2001 at 01:09:47PM -0500, Ciprian I. Acatrinei wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. If you're sure it will meet your needs and you already know that it costs less, the other big benefit is the support. MySQL support is very good (and inexpensive). I don't know of many MSSQL server users who have mailed bug reports directly to the core developers and received a response in less than 12 hours... Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL vs Microsoft SQL
Is there something that you can do with MS SQL and you can not do with MySQL? At 04:01 PM 3/23/2001, Jeremy D . Zawodny wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* On Fri, Mar 23, 2001 at 01:09:47PM -0500, Ciprian I. Acatrinei wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. If you're sure it will meet your needs and you already know that it costs less, the other big benefit is the support. MySQL support is very good (and inexpensive). I don't know of many MSSQL server users who have mailed bug reports directly to the core developers and received a response in less than 12 hours... Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 Ciprian I. Acatrinei IT Manager Mafcote Inc. 108 Main Street, Norwalk, CT 06851 tel: 203-847-8500 fax: 203-849-9177 mailto:[EMAIL PROTECTED] http://www.mafcote.com
Re: MySQL vs Microsoft SQL
platform independency, reasonable portability, performance(!), optimal load/performance ratio, loads of access methods including odbc and web based scripts like php,asp, active development, integration with apache authentication, very very good personal online help (this mailing list :), low network traffic (ie: good performance when client server are not on the same machine), reasonable ansi-92 sql compliance except for a few issues, automatic incrementing primary keys (w/o stored procedures), usable from java, perl, c, c++, delphi, kylix, php, apache, almost: name it, platform indepent, environment indepent, future safe (ie: not a dead end in computer history) - Original Message - From: "Ciprian A." [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, March 23, 2001 7:35 PM Subject: MySQL vs Microsoft SQL *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. Thanks, Ciprian A. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL vs Microsoft SQL
When was the last time you got to ask a question directly to one of the developers of MS SQL? When was the last time you found a bug in MS SQL and one of the developers told you it would be fixed tonight and to go grab the source tomorrow and recompile? When was the last time you could buy OFFICIAL support for MS SQL for $200? How often have you been invited to take a look at the source code and see how we did it. (That's actually in the MySQL manual at one point!) When was the last time a MS SQL developer told you "if you don't like the way it works, fix it your own damn self"...and you COULD? When was the last time MS released a new version and there was a feature you didn't want so you re-compiled it WITHOUT the new code? If you are looking for liability and culpability in case something goes wrong, I suggest you read you MS license. If something goes wrong and MS SQL tanks and destroys your company and leaves a smoking crater where your house used to be, there is NOTHING you can do about it. (Not that I can sue the MySQL developers either, but at least they are honest about it.) There are some applications where I wouldn't use MySQL, that MS SQL might be the right choice. (I can't think of any now, but work with me here) MS SQL is big, bloated and 'feature laden'. I need a fast RDBMS. I don't need built-in email support, I don't need a built-in CRON, I don't need a pretty GUI, and I CERTAINLY don't need built-in XML support! But with MS SQL I have all of these and so much more. I know because I have a database running on MS SQL right now. I had to purchase a development license, then a production license, pay the extra fee for using it on the web (how dare I!) and if I actually need help because it's got bugs, I have to pay again! #1 reason to use MySQL over MS SQL, because you can. HTH, IMHO, etc. Cal http://www.calevans.com -Original Message- From: Ciprian I. Acatrinei [mailto:[EMAIL PROTECTED]] Sent: Friday, March 23, 2001 12:10 PM To: [EMAIL PROTECTED] Subject: MySQL vs Microsoft SQL *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. Thanks, Ciprian A. - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: MySQL vs Microsoft SQL
A whole TODO list of things. One should really evaluate the pros and cons of both databases to make an educated decision on which system would better suit ones needs. "Ciprian I. Acatrinei" wrote: Is there something that you can do with MS SQL and you can not do with MySQL? At 04:01 PM 3/23/2001, Jeremy D . Zawodny wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* On Fri, Mar 23, 2001 at 01:09:47PM -0500, Ciprian I. Acatrinei wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. If you're sure it will meet your needs and you already know that it costs less, the other big benefit is the support. MySQL support is very good (and inexpensive). I don't know of many MSSQL server users who have mailed bug reports directly to the core developers and received a response in less than 12 hours... Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 328-7878Fax: (408) 530-5454 Cell: (408) 439-9951 Ciprian I. Acatrinei IT Manager Mafcote Inc. 108 Main Street, Norwalk, CT 06851 tel: 203-847-8500 fax: 203-849-9177 mailto:[EMAIL PROTECTED] http://www.mafcote.com - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
RE: MySQL vs Microsoft SQL
For what it's worth, here's my $0.02... -- Is there something that you can do with MS SQL and you can not do with MySQL? MSSQL - has support for triggers, stored procedures, views, XML, and transactions. I would mention subqueries, but subqueries are on the way with mySQL. MySQL - doesn't have all these fancy bells and whistles, but I believe it has a lot to do with how you look at things, is the cup of water half-full or half-empty? I will say that mySQL has a mailing list that many developers around the world access and can help you with your problems (1. provided you've made an effort to solve it), so just on that note, the support is well worth it. Not only that, but mySQL "forces" you to learn SQL. Not by wizards that build the SQL statement for you. Like J. Zawodny says, if it meets your needs, then do it. At 04:01 PM 3/23/2001, Jeremy D . Zawodny wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* On Fri, Mar 23, 2001 at 01:09:47PM -0500, Ciprian I. Acatrinei wrote: *This message was transferred with a trial version of CommuniGate(tm) Pro* Hi, I would need some reasons for choosing MySQL instead of Microsoft SQL. (beside the fact that MySQL is free). (not for me but for my boss). It may sound silly but trust me I really need these reasons. So please help me with this. If you're sure it will meet your needs and you already know that it costs less, the other big benefit is the support. MySQL support is very good (and inexpensive). I don't know of many MSSQL server users who have mailed bug reports directly to the core developers and received a response in less than 12 hours... - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
