| |
|
If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
|
 |

11-01-07, 13:44
|
|
Window Washer
|
|
Join Date: Nov 2002
Location: Jersey
Posts: 10,303
|
|
|
I must enter a title first
|
|
I'm at the mySQL site, and I'm looking for a download, but all I see is some Enterprise version that you have to purchase?
I thought it was suppose to be free
|
|

11-01-07, 13:47
|
|
Registered User
|
|
Join Date: Nov 2003
Posts: 2,407
|
|
|
|

11-01-07, 13:48
|
|
Jaded Developer
|
|
Join Date: Nov 2004
Location: out on a limb
Posts: 9,262
|
|
|
|

11-01-07, 13:57
|
|
SQL Consultant
|
|
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,534
|
|
why bother, brett? everyone will tell you that mysql, yes, and postgresql, cannot be any good, because they're OSDBs (open sores databases)
two mister winkies, in case you thought i was serious
|
|

11-01-07, 14:39
|
|
Window Washer
|
|
Join Date: Nov 2002
Location: Jersey
Posts: 10,303
|
|
my boss is doing a side project and wants to jump from sql server
|
|

11-01-07, 18:03
|
|
www.gvee.co.uk
|
|
Join Date: Jan 2007
Location: UK
Posts: 10,156
|
|
Just out of interest - is there any reason why he wants to try something different?
|
|

11-01-07, 18:04
|
|
Registered User
|
|
Join Date: Nov 2003
Posts: 2,407
|
|
Quote:
|
Originally Posted by Brett Kaiser
my boss is doing a side project and wants to jump from sql server
|
Although written by a Postgres-biased company, this comparison might be interesting for you. It's not the usual "bash-the-other-product" type of comparison.
http://postgres.enterprisedb.com/whyPostgres.jsp
|
|

11-01-07, 18:47
|
|
SQL Consultant
|
|
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,534
|
|
|
|

11-01-07, 19:28
|
|
Registered User
|
|
Join Date: Nov 2003
Posts: 2,407
|
|
Quote:
|
Originally Posted by r937
|
I agree, and it's a very nice comparison, but it I wouldn't base my choice of a DBMS only on the syntax differences 
|
|

11-01-07, 19:34
|
|
SQL Consultant
|
|
Join Date: Apr 2002
Location: Toronto, Canada
Posts: 19,534
|
|
Quote:
|
Originally Posted by shammat
I wouldn't base my choice of a DBMS only on the syntax differences 
|
me neither
availability of skilled DBAs and vendor support come first and second, which pretty much means only SQL Server, DB2, and Oracle (in that order) would qualify for any serious big implementations

|
|

11-02-07, 05:10
|
|
Registered User
|
|
Join Date: Nov 2003
Posts: 2,407
|
|
Quote:
|
Originally Posted by r937
me neither
availability of skilled DBAs and vendor support come first and second, which pretty much means only SQL Server, DB2, and Oracle (in that order) would qualify for any serious big implementations

|
Interesting order. I have no experience with DB2 so I cannot judge. But I'd choose Oracle over SQL Server anytime. Especially in high transactional system where readers will block writers in SQL Server. The locking granularity of SQL Server (and MySQL btw) is just not good enought to allow for a good throughput.
But I have to admit that I haven't worked with SQL Server for quite a while, so I have no experience with newer versions where SQL Server apparently has now MVCC as well, and readers and writers should not block each other any more.
|
|

11-02-07, 08:09
|
|
Resident Curmudgeon
|
|
Join Date: Feb 2004
Location: In front of the computer
Posts: 12,609
|
|
I've worked with all three databases, and I really prefer Microsoft SQL although when you configure MySQL correctly (which is unusual, but possible) the difference is negligable.
The advantage that I see for concurrancy is that Oracle's MVCC allows readers to not be blocked by writers. This is the default, and as far as I know only configuration for Oracle. It is a lovely thing when you look simply at database performance, because it allows the pending reads to complete without even being aware of pending writes... Therin lies the problem!
When you are creating applications that deal with either security or money, blythely ignoring a writer is an invitation to disaster. This allows you (or more accurately the user) to make decisions based on incomplete data because you (the programmer/application) could know that the data is changing underneath you!
Microsoft SQL allows you to set the isolation level several different ways. At the default isolation setting, MS-SQL will allow the writers to block the readers to ensure that once a result set is returned, it is both correct and complete. At the most relaxed setting, MS-SQL is a bit more forgiving than Oracle can be, allowing readers to be completely unaware of writers. At the strictest setting, the readers will not only block the writers against present data but also against inserting new data that would corrupt a re-read of the data!
As I commented in a recent MySQL thread, I like options that (once I understand the consequences) I can set to get the database engine to perform the way that I'd like!
-PatP
|
|
| Thread Tools |
Search this Thread |
|
|
|
| Display Modes |
Linear Mode
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
|
|