Orbit

To add on to the two statements already, PostgreSQL is going to give you what you already would be getting with MySQL - but is also very at handling geospatial information.

So if you plan on mapping your water/power database (even if it's billing) to something spatial, Postgre would be better at handling the spatial data than MySQL or MSSQL.

I don't quite 100% understand the technical backing behind Postgres/MySQL for GIS related/mapping things. I just understand that it's very math heavy and Postgre handles it much better than MySQL does.

-- Andrew Berquist, Acting Chief Technology Officer

Information Technology Department American Samoa Government 50001 EOB Loop A.P. Lutali Executive Office Building Pago Pago, American Samoa 96799 Office: 1-684-633-3649/3650 Mobile: 1-684-252-7219 Fax: 1-684-633-3651 Email: andrew.berquist@itd.as.gov

On Fri, Apr 20, 2012 at 9:12 PM, Phil Regnauld regnauld@nsrc.org wrote:

Tepatasi Lealofi (tepatasi) writes:

...

Tarau,

I would not recommend Access. Access is very limited in both features

and file capacity. Both Microsoft SQL Server and MySQL are excellent choice, one is free (but recommend to pay for support) and the other you have to pay big bucks to Micro$oft. Both DB engines have various differences in SQL syntax and features. It also depends on how you design your application. Are you going to use many Stored Procedure, Views, etc.

...

Finally, if you are using PHP as your development tool, MySQL would

probably be a better choice. If you are using Visual Studio or any other MS tools, then i suggest to stick with MS SQL Server.

    To add to these comments, I would strongly suggest considering

PostgreSQL instead of MySQL. PostgreSQL implements all SQL Server features, and most of what DBs like Oracle has to offer. PostgreSQL is also open source and free, and there are enterprise commercial versions where you can buy support.

   For management and design of the DB Schema, you can look at a

number of products such as SQL Power Architect and pgAdmin3.

   Cheers,
   Phil

---

pacnog mailing list pacnog@pacnog.org http://mailman.apnic.net/mailman/listinfo/pacnog

Thanks everybody for your reply, I got something to start with maybe I'll take an opensource.

best regards On Sun, Apr 22, 2012 at 8:42 AM, Hervey Allen hervey@nsrc.org wrote:

On 4/21/12 6:51 AM, Tepatasi Lealofi wrote:

...

Tarau,

I would not recommend Access. Access is very limited in both features and file capacity. Both Microsoft SQL Server and MySQL are excellent choice, one is free (but recommend to pay for support) and the other you have to pay big bucks to Micro$oft. Both DB engines have various differences in SQL syntax and features. It also depends on how you design your application. Are you going to use many Stored Procedure, Views, etc.

Finally, if you are using PHP as your development tool, MySQL would probably be a better choice. If you are using Visual Studio or any other MS tools, then i suggest to stick with MS SQL Server.

Good luck.

I would note that if you go the Open Source SQL route the other mainstream database choice is PostgreSQL - A very robust, full-featured and open database. You can read about PostgreSQL here:

http://www.postgresql.org/

MySQL is here:

http://www.mysql.com/

If you read their pages you'll see how widely used they are.

Best of luck!

• Hervey Allen

-- Hervey Allen Network Startup Resource Center hervey@nsrc.org http://nsrc.org/ : http://facebook.com/nsrc.org GPG Fingerprint: AC08 31CB E453 6C65 2AB3 4EDB CEEB 5A74 C6E5 624F _______________________________________________ pacnog mailing list pacnog@pacnog.org http://mailman.apnic.net/mailman/listinfo/pacnog