Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Linux Open Source Database Server Questions

Status
Not open for further replies.

CygnusX33

Programmer
Jan 12, 2003
2
US
I am in need of first hand accounts and advise from people who have experience with linux and Open Source Database Servers. I am going to set up an Open Source Database Server on a Red Hat 8 intel box. I am leaning toward MySQL or PostgreSQL.

I am hoping to gain information concerning:

Applications used, Ones to stay away from, setup problems, compatability with windows and access queries, and overall general advice. Thank You all for your time and effort.
 
CygnusX33 wrote:

>Applications used, Ones to stay away from, setup problems, compatability with windows and access queries, and overall general advice.

1. Applications used --

PostgreSQL has some great applications, such as (windows admin tool)
(PHP admin tool)

The only application I ever used to administrate MySQL was
Both of these database systems support ODBC, thus working fine with most 3rd-party E/R design tools, and reporting tools. However, PostgreSQL has much better ANSI-standard SQL, which might work better with some of these tools.

2. Ones to stay away from --
Oh, that's too broad a category ;-). Just stay away from anything that relies too heavily on buzzwords and marketspeak.

3. Setup problems --
MySQL may be slightly easier to set up, but really either one is kind of a standard package for most Linux systems, so you probably won't have to do any setup at all. I personally tend to prefer compiling from source when I install. Both PostgreSQL and MySQL can be compiled from source, and setup, simply by following one page of instructions. I have never had a serious setup problem with either. PostgreSQL is a little more complex to manage, but that is because it has much more capability. But, if you use PGAdmin (linked above) you really will have a nice time of it. PGAdmin is very much like a commercial database administrator tool.

4. Compatibility with Windows --
The MySQL server can be installed easily on Windows. PostgreSQL server is still not able to run natively on Windows. It can be run using the Cygwin Unix compatibility system. Also, there is work on a beta which runs in native mode on Windows, but it won't be ready for a few months.

However, the PostgreSQL client environments support Windows just fine. I would also argue that PostgreSQL supports more ODBC and JDBC standards, since its functionality is more similar to the major DBMS systems, such as Oracle, DB2, Sybase, SQL Server, etc... Either system can be used as an Access client, but remember, that they won't work as smoothly as SQL Server itself. Mainly with PostgreSQL and MySQL, you will have to define your foreign key constraints manually, because changing the Relationships view in Access won't directly affect the SQL constraints.

5. Overall general advice --

Go with PostgreSQL if your data is critical to your system's success. Especially if you want to define business rules in your database. (something that MySQL cannot do at all right now). MySQL is fine for lightweight databases, dynamic websites, list management, etc... Since I switched to PostgreSQL, though, I have never ever felt the need to use MySQL for anything :-/. -------------------------------------------

PHP/Perl/SQL/Javascript --
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top