in reply to MySQL vs SQL2000

There are IMHO 3 major differences between MySQL and SQLServer.

  • MySQL does not support stored procedures
  • MySQL does not support subqueries
  • SQLServer only supports 1 statement handle per DB connection

    • All of these can be coded around, but I would strongly urge you to consider PostgreSQL (Which has none of those 3 limitations). PostgreSQL only has one thing I consider a limitation, which is lack of formal replication support (which there are several informal methods). If you really want to get into the minutia you can compare all 3 with crash-me

    As side notes (read: just my opinion)-

    I really don't care for SQLServer's logging, to me it seems very much feast or famine - You are either wading through hundreds of worthless messages or you get almost nothing.

    MySQL transaction support is fairly new. (not that it's bad, just new)



    grep
    Mynd you, mønk bites Kan be pretti nasti...

    Replies are listed 'Best First'.
    Re: Re: MySQL vs SQL2000
    by true (Pilgrim) on Oct 22, 2002 at 05:06 UTC
      perfect. crash-me has some solid numbers without the sales jargon. thanks tons.
      PostgreSQL looks very very impressive.
      This Page claims native Windows compatibility will be introduced with PostgreSQL 7.4.
      MSSQL Server seemed to support a larger character structure and db size than regular MySQL.
      crash-me comparison claimed the following:
    • MSServer supports 1000 simultaneous connections
    • PostgreSQL supported 32 simultaneous connections
    • MySQL supported 101 simultaneous connections
    		[reply]
        About the simultaneous connections: You must also keep in mind that these are the default installation values, that doesn't mean that PostgreSQL doesn't support more that 32 simultaneous connections, you just have to tweak the configuration file to make it possible. To me that output is just useless data, it doesn't speak about maximum values and/or scalability at all....
        --
        use signature; signature(" So long\nAlfie");
    		[reply]

          To further expand on alfie - PostgreSQL's connection limit can be upped arbitrarily but that's limited by the amount operating system's shared memory. When I install PostgreSQL on OpenBSD I have to make a tweak to the kernel to up the maximum limit. This is all documented so it's nothing to worry about but it would be misleading to simply look at PostgreSQL's arbitrary 32 connection limit and ignore the OS's less but still arbitrary limit.

          __SIG__
printf "You are here %08x\n", unpack "L!", unpack "P4", pack
  "L!", B::svref_2object(sub{})->OUTSIDE;

          [download]
    		[reply]
    [d/l]
        If anyone has upped the limit with PostgreSQL, please indicate how many simultaneous connections they were able to add. I know this will vary from OS architecture, but a rough figure would help. The speed of the query is also very important. That will drastically effect performance and tweek the simultaneous connections summary as well. According to crash-me, MySQL offers blazing SELECT query speed for example.
    		[reply]

    In Section Seekers of Perl Wisdom