Re: [pacnog] MYSQL vs SQL Server
- To: Phil Regnauld <regnauld at nsrc dot org>
- Subject: Re: [pacnog] MYSQL vs SQL Server
- From: Andrew Berquist <andrew.berquist at itd dot as dot gov>
- Date: Fri, 20 Apr 2012 21:28:05 -1100
- Cc: "pacnog at pacnog dot org" <pacnog at pacnog dot org>
- Delivered-to: pacnog at mailman dot apnic dot net
- In-reply-to: <20120421081222.GA86898 at macbook dot bluepipe dot net>
- List-archive: <http://mailman.apnic.net/mailing-lists/pacnog>
- List-help: <mailto:firstname.lastname@example.org?subject=help>
- List-id: Pacific Network Operators Group <pacnog.pacnog.org>
- List-post: <mailto:email@example.com>
- List-subscribe: <http://mailman.apnic.net/mailman/listinfo/pacnog>, <mailto:firstname.lastname@example.org?subject=subscribe>
- List-unsubscribe: <http://mailman.apnic.net/mailman/listinfo/pacnog>, <mailto:email@example.com?subject=unsubscribe>
- References: <CAARtr3iRxj51GHz1+WHpfUkF44ECfqfT7E4BT1OxZHBryoRSbw@mail.gmail.com> <1334980319.14608.YahooMailNeo@web1208.biz.mail.gq1.yahoo.com> <20120421081222.GA86898@macbook.bluepipe.net>
- Sender: firstname.lastname@example.org
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.
Acting Chief Technology Officer
Information Technology Department
American Samoa Government
50001 EOB Loop
A.P. Lutali Executive Office Building
Pago Pago, American Samoa 96799
On Fri, Apr 20, 2012 at 9:12 PM, Phil Regnauld <regnauld at nsrc dot org> wrote:
Tepatasi Lealofi (tepatasi) writes:To add to these comments, I would strongly suggest considering PostgreSQL
> 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.
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
For management and design of the DB Schema, you can look at a number of
products such as SQL Power Architect and pgAdmin3.