Comments on: We are developing an information system to capture client information. Which database should we use? http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/ Wed, 14 Dec 2011 05:50:23 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: mehmet_avsar http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/comment-page-1/#comment-3994 mehmet_avsar Fri, 14 May 2010 14:49:24 +0000 http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/#comment-3994 Well, "My girl friend should be a b*tch, i want my wife virgin" . If you're hosting your server in-house, you'll probably can't afford Oracle or MS SQL. In fact, you shouldn't. MySQL is no more less scalable, affordable, reliable and secure than "the others". If you stuck between PostgreSQL and MySQL, choose MySQL for it's speed (though PostgreSQL is also speeding up), and PostgreSQL for it's native RDBMS features like triggers, procedures. MySQL requires 3rd party InnoDB storage engine, and it's acquired by someone else :) No need to panic, MySQL immediately replaced it by Falcon on it's 5.2 releases. I am currently using MySQL for a corporate sales project, and it's still working soooo fast after 2.5 million records. All good. Well, “My girl friend should be a b*tch, i want my wife virgin” .

If you’re hosting your server in-house, you’ll probably can’t afford Oracle or MS SQL. In fact, you shouldn’t. MySQL is no more less scalable, affordable, reliable and secure than “the others”.

If you stuck between PostgreSQL and MySQL, choose MySQL for it’s speed (though PostgreSQL is also speeding up), and PostgreSQL for it’s native RDBMS features like triggers, procedures. MySQL requires 3rd party InnoDB storage engine, and it’s acquired by someone else :)

No need to panic, MySQL immediately replaced it by Falcon on it’s 5.2 releases.

I am currently using MySQL for a corporate sales project, and it’s still working soooo fast after 2.5 million records. All good.

]]> By: dhvrm http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/comment-page-1/#comment-3993 dhvrm Fri, 14 May 2010 14:08:26 +0000 http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/#comment-3993 MySQL should fit your needs fine. You can populate a mail merge with Microsoft Word, using ODBC drivers for MySQL, which are freely distributed with MySQL. You can also export MySQL to ACT via ODBC. MySQL should fit your needs fine.

You can populate a mail merge with Microsoft Word, using ODBC drivers for MySQL, which are freely distributed with MySQL. You can also export MySQL to ACT via ODBC.

]]> By: MacGuru http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/comment-page-1/#comment-3992 MacGuru Fri, 14 May 2010 14:05:44 +0000 http://www.someproxy.com/we-are-developing-an-information-system-to-capture-client-information-which-database-should-we-use/#comment-3992 Yes, I would use MySQL. It's the most widely-used and flexible database. Yes, I would use MySQL. It’s the most widely-used and flexible database.

]]>