Results 1 to 8 of 8

Thread: MySQL or MSSQL?

  1. #1
    Proware's Avatar
    Proware is offline A Prolific Poster
    Join Date
    Mar 2006
    Location
    Sydney Australia
    Posts
    310

    Default MySQL or MSSQL?

    Assuming money was no object, would you choose MySQL or MSSql as the database for a 10 user Sugar CRM implementation and Why?

    Background - I am creating a new server and am contemplating moving my current Sugar on MySQL over there or converting it to MSSQL on the new new server.

    I have already played around with converting my data to MSSql with some success and so am looking for the Pro's and Cons.

    Once thing I have noticed is that MSSQL seems to use about 1.7GB Ram in it's default configuration whereas MSSQL uses about 700MB Ram with my current configuration.

    Any guidance is appreciated.
    Cheers

    David Younger
    TSM - The Service Manager
    http://www.theservicemanager.com


    Operating system type and version: Windows 2003 Server
    » Sugar Suite version 4.5.1e Professional
    » Webserver type and version Microsoft-IIS/6.0
    » PHP version 5.2.6
    » MySQL server version 5.0.51a

  2. #2
    al3
    al3 is offline Sugar Community Member
    Join Date
    Aug 2007
    Posts
    394

    Default Re: MySQL or MSSQL?

    I would never use an M$ product when there is a comparable free or low-cost product instead. I've been using MySQL for ten years now in all sorts of applications and have never had a problem with it. It is safe, secure, solid, fast, and low-cost (or free.) M$ brings nothing to the table that is even remotely worth the price.

    Al
    http://www.insurancesolutions123.com

  3. #3
    JVWay is offline Sugar Community Member
    Join Date
    Sep 2007
    Location
    Corvallis, Oregon
    Posts
    452

    Default Re: MySQL or MSSQL?

    Agree with al3, even if money were no object MS products just aren't worth the additional hassle. But also, why spend more when you don't have to?

    I started with Sugar trying to get the mssql thing working and it was a pain. Even with the additional work done with the connector it was a lot harder.

    Additionally, you are then stuck on a complete MS stack and that's going to increase your difficulties. There are plenty of utilities and tools to get to the MYSQL data. Look into Talend's open studio, or OpenOffice.org's Base. You can access mysql with ODBC or JDBC.

    You're also right that it doesn't use nearly the resources.

    Also, creating a cluster of mysql servers is much, much easier than with SQL server. It's just a matter configuring a couple of files and you've got your master/slave. With SQL server your going to end up with enterprise version and a huge management issue.

    I could go on, but to sum up go with MySql.
    Jerry Way
    Business Process Administrator

    Sugar 6.1.4 Professional
    (Testing 6.1.2)
    LAMP on Centos 5
    PHP 5
    MySQL 5
    Apache 2.2

  4. #4
    kuske's Avatar
    kuske is offline Sugar Community Member
    Join Date
    Oct 2007
    Location
    Germany
    Posts
    2,597

    Default Re: MySQL or MSSQL?

    My PROs of MySQL:

    • Administration is simple
    • Backup and Restore are simple in sql Textfiles, mssql is very complex
    • All Admin tools are available for free, in mssql they are only included in the commercial version
    • Sugar seems to run better with mysql, I saw some ugly problems here in the forum
    • MySql is no memory eater, mssql uses all available memory
    • MySql is full integrated in XAMPP, which allows simple start/stop admin of DB and Apache
    • MySql runs on different platforms (unix, windows,...)

    My PROs of MSSQL:

    • Commercial Product ( yes $s can be a PRO )
    • Good for great amount of data (clusters are possible)
    • Faster than MySQL on great data amounts
    • Better integration in MS-Office products

  5. #5
    roblaus's Avatar
    roblaus is offline Sugar Community Member
    Join Date
    Dec 2006
    Location
    Vienna / Austria
    Posts
    2,850

    Default Re: MySQL or MSSQL?

    I always liked MSSQL for its DTS. Used correctly it can do many of your possibly needed im- and export routines automatic including error checks, dependencies and what have you. In MySQL I haven't found anything like that.
    But this would be my only MSSQL pro statement.
    __________________________
    Robert Laussegger
    http://www.iscongroup.net

    Bei Fragen: support@iscon.at
    Die deutschen Sprachdateien für SugarCRM und das deutsche Handbuch gibt es hier: http://goo.gl/kPsAz
    Ab sofort auch mit 6.4.2

  6. #6
    JVWay is offline Sugar Community Member
    Join Date
    Sep 2007
    Location
    Corvallis, Oregon
    Posts
    452

    Default Re: MySQL or MSSQL?

    Quote Originally Posted by roblaus
    I always liked MSSQL for its DTS. Used correctly it can do many of your possibly needed im- and export routines automatic including error checks, dependencies and what have you. In MySQL I haven't found anything like that.
    But this would be my only MSSQL pro statement.
    Did you see what they did to DTS in 2005? You now have to install a significant portion of the Visual Studio monster to enable DTS like stuff.

    If you want DTS capabilities plus a whole lot more look into Talend Open Studio. It's pretty amazing.
    Jerry Way
    Business Process Administrator

    Sugar 6.1.4 Professional
    (Testing 6.1.2)
    LAMP on Centos 5
    PHP 5
    MySQL 5
    Apache 2.2

  7. #7
    Deuce is offline Sugar Community Member
    Join Date
    Aug 2006
    Location
    California
    Posts
    66

    Default Re: MySQL or MSSQL?

    Quote Originally Posted by JVWay
    Did you see what they did to DTS in 2005? You now have to install a significant portion of the Visual Studio monster to enable DTS like stuff.

    If you want DTS capabilities plus a whole lot more look into Talend Open Studio. It's pretty amazing.
    I was horrified when I saw what they did to DTS in 2005. Leave it to MS to take the best pieces out of a product for the next version.
    Still, our Sugar install runs on the mssql server. We have some automated sql data feeds going from Sugar into some legacy apps, and back out to Sugar too, which is pretty simple to set up using mssql.

    We run Linux/mysql as well on other servers for other purposes, but in this case mssql was the logical choice, for us anyway.

  8. #8
    Proware's Avatar
    Proware is offline A Prolific Poster
    Join Date
    Mar 2006
    Location
    Sydney Australia
    Posts
    310

    Default Re: MySQL or MSSQL?

    Thanx for all the feedback.

    I have decided to stick with MySQL.

    I have installed it on a new server and it is about 3 times faster than on the old server. Don't quite know what the difference is but I am very happy with the outcome.

    Thanx for all the feedback.
    Cheers

    David Younger
    TSM - The Service Manager
    http://www.theservicemanager.com


    Operating system type and version: Windows 2003 Server
    » Sugar Suite version 4.5.1e Professional
    » Webserver type and version Microsoft-IIS/6.0
    » PHP version 5.2.6
    » MySQL server version 5.0.51a

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Query Failed: AND users.id = '1'::MySQL error 1064:
    By artco001 in forum Installation and Upgrade Help
    Replies: 63
    Last Post: 2009-05-07, 05:56 AM
  2. Replies: 5
    Last Post: 2007-11-13, 02:51 PM
  3. MySQL Database Not Available
    By luisamato in forum Help
    Replies: 4
    Last Post: 2007-06-27, 05:58 AM
  4. Huge backups -- normal?
    By Liam in forum Help
    Replies: 5
    Last Post: 2007-05-02, 05:36 AM
  5. MySQL error/no workflow notifications
    By rlbyrd in forum Help
    Replies: 1
    Last Post: 2006-09-11, 09:14 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •