SQL Server 2008: ARITHABORT error with Spatial data

This is a nice cryptic error:


UPDATE failed because the following SET options have incorrect settings: 'ARITHABORT'. Verify that SET options are correct for use with indexed views and/or indexes on computed columns and/or filtered indexes and/or query notifications and/or XML data type methods and/or spatial index operations. 

If you get the following error with a SQL Server 2008 database when your trying to update some spatial data, the solution is to check the compatibility level for the database, I was working on an application which has been around for a while and it was set to be compatible with Sql Server 2000, hence the error.

I was a bit stumped initially, as this was my first look into spatial data with MS SQL Server, luckily Jackie Ng sits next to me and he found the solution pretty quickly.

Overall, my initial impressions of the Spatial support in SQL Server is that it's pretty basic compared to Oracle which is a much more complete implementation, but I'm glad spatial is finally a standard feature. I am rather surprised that re-projection is not part of the standard feature set.

I really loathe Oracle for it's recalcitrant attitude to Oracle Spatial licensing, but having seen what Sql Server offers, I understand why Oracle still does what it does, as SQL Server is not nearly equivalent.

Of course, IMHO anyone starting out on a new project requiring a spatial database should use PostGIS period.