Nothing beats PostGIS at the moment and there is a large migration of GIS databases going on in general where the free and free ( code and license) aspects of Postgre are major factors as well. In my job I am running and coding for Postgre, MySQL and MSSQL servers and have previously over the past decades developed in DB2, Oracle and others. Administration is never fool proof - database flavor doesn't matter much there.Moving from Postgre would be swimming against the tide. -------- Upprunalegt skeyti --------Frá: John Whelan <jwhelan0...@gmail.com> Dagsetning: 24.7.2020 23:03 (GMT+00:00) Til: Hartmut Holzgraefe <hart...@php.net> Samrit: talk@openstreetmap.org Efni: Re: [OSM-talk] Heresy - pure discussion Thank you Hartmut,
my expertise is not in GIS databases so this is helpful to know. My experience is much more to do with straight SQL databases doing none GIS work on a variety of platforms. Cheerio John Hartmut Holzgraefe wrote on 2020-07-24 18:49: On 25.07.20 00:16, Alexandre Oliveira wrote: Having said that the main advantage of SQL is it is a standard so you should be able to connect practically anything to it. That's not entirely true. SQL is a language but every database implements its own dialect, i.e., some query keywords implemented in MSSQL might not be available in MySQL/MariaDB and vice-versa. SQL is a "standard" only in so far as developers are somewhat interchangeable between products. There is nothing that prevents RDBMS implementations from adding features on top of the standard, and most of the standard features are optional anyway. E.g. the actual ISO SQL standard for stored procedures is only really implemented by IBM/DB2, MySQL and MariaDB, while all other RDBMS products implement their own procedure languages (and I can't even blame them, as the ISO SQL standard syntax feels as if it got stuck in the old BASIC days). The key question though would be: is MS SQL Server GIS support on par with PostGIS? My impression so far was that it provides just a little bit more than what the OGC 1.1 standard requires. That would put it in the same league as MySQL and MariaDB, maybe slightly ahead, but very far below what PostGIS provides. (Disclaimer: I'm working for MariaDB as a support engineer, and have been working for MySQL before, so I may a little bit biased. But even I would always recommend the PostgreSQL / PostGIS combo over MariaDB for all but the most basic GIS applications) -- Sent from Postbox
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
