Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6

BostonGIS BostonGIS Home About Postgres OnLine Journal PostGIS in Action

Saturday, July 19. 2008

Posted by Regina Obe in foss, microsoft, mysql, postgis postgresql, sql server 2008

Comments (11)
Trackback (1)

Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6

A few people have been asking us what are the pros and cons of using SQL Server 2008 Spatial and PostGIS and as a Windows user, why would you still consider using PostGIS. Rather than simply providing some hand-waving saying "well if you just care about displaying data, then use whatever you feel comfortable with, but if you want to do real intensive sophisticated spatial analysis and geometric processing without having to purchase a bunch of expensive software, then PostGIS is probably better for you. Hell why must you think in either or propositions - just use both using the strengths of each.", we have tried really hard to quantify the similarities and differences between the 2 and to boot - we have also added in MySQL.

Our analysis can be found at Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6

If you have any comments, suggestions of additions, things you felt we got wrong, then please don't hesitate to comment and we'll try to update our survey.

Trackbacks

Trackback specific URI for this entry

SQL Server 2008 R2, Oracle 11G R2, and PostGIS/PostgreSQL spatial compares
Spatial compares of the top 3 commonly used spatial databases Last time we did a survey such as this Cross Compare SQL Server 2008 Spatial, PostgreSQL/PostGIS 1.3-1.4, MySQL 5-6 we had in our mix MySQL instead of Oracle. Many people wanted to see Oracl

Weblog: BostonGIS Blog
Tracked: May 29, 16:00

Comments

Display comments as (Linear | Threaded)

Hi! Nice to see an article that covers the strengths and weaknesses of the various platforms and a realistic outlook on why various shops may choose one or the other. Just a quick note: MapGuide Open Source also supports SQL Server 2008 if you use a beta FDO provider, but you may need to pull the latest provider and compile it yourself for the new axis order stuff. I did a bit of testing with an earlier version, and it works relatively well. http://www.jasonbirch.com/nodes/2008/03/05/170/mapguide-open-source-serves-up-sql-server-spatial/ Some of the statements I made there (such as MS relaxing geometry strictness) are likely incorrect though.

#1 Jason Birch (Homepage) on 2008-07-19 20:13 (Reply)

Thanks Jason, We updated to reflect that.

#1.1 Leo (Homepage) on 2008-07-20 07:15 (Reply)

SQL Server 2008 RC0 also supports Z and M values, similar to MySQL. In the table it looks like that isn't supported at all.

#2 Morten (Homepage) on 2008-07-21 16:00 (Reply)

Thanks Morten. We've updated. You know off hand if SQL Server 2008 does anything with M and Z or can it e.g. is the ST_Length function take into consideration the Z axes like PostGIS ST_Length3D does? I couldn't easily tell from the docs and haven't gotten that far in my exploration.

#2.1 Regina (Homepage) on 2008-07-22 18:13 (Reply)

Good survey. A couple edits/corrections to the SQL Server info: - I'm not quite sure what you mean by "Various levels of features based on version, Free Crippleware". To clarify, overall this is true (although I might debate the "Crippleware" note) but there are no spatial-specific limitations in any edition. - STDistance on geography no longer has the point limitation. (BOL needs to be fixed---docs bug opened!) - You are correct that you have to roll your own aggregates today, but you can also roll your own functions like linear referencing. I'll try to post some examples. Cheers, -Isaac

#3 Isaac Kunen (Homepage) on 2008-07-21 20:02 (Reply)

Thanks Isaac. I agree we should have clarified that the spatial support is fully supported in express, but there is the memory-size, processor limitation. Which is vastly less annoying than Oracle requiring Enterprise version to get the real deal. We'll update but try to be less verbose than that. We'll also correct the distance and put in comment about linear referencing. When you are done with your examples, we'll add a link to those.

#3.1 Leo (Homepage) on 2008-07-21 20:16 (Reply)

Good work. I suggest one more feature: "Free Object/Relational Mapping". Hibernate Spatial supports PostGIS, MySQL and Oracle. NHibernate.Spatial supports PostGIS, MsSqlSpatial and SQL Server 2008 (RC0). http://www.hibernatespatial.org/ http://www.codeplex.com/NHibernateSpatial

#4 Ricardo Stuven on 2008-07-21 23:08 (Reply)

Ricardo, Thanks for the tidbit. We've added Free Object/Relational Mapping to the list.

#4.1 Regina (Homepage) on 2008-07-22 18:16 (Reply)

Great work, Regina, as usual ;-)

#5 Paolo (Homepage) on 2008-07-23 12:47 (Reply)

Thanks

#5.1 Regina on 2008-07-23 14:03 (Reply)

Add Comment

Name
Email
Homepage
In reply to
Comment	E-Mail addresses will not be displayed and will only be used for E-Mail notifications. To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly. Enter the string from the spam-prevention image above:
	Remember Information? Subscribe to this entry