SQL Server 2008 - Geometry Data Type

It's official.  ESRI has recommended that we don't use the GEOMETRY data type in SQL SERVER 2008 for versioned data.  Maybe they'll do a better job with it for ArcGIS 9.4.

Quantum GIS - PostGIS

I completely geeked out this morning and was goofing around with QGIS and postGIS.  Normally I do my shapefile-->postGIS loads from command-line.  I loaded Quantum GIS last night and found the "Import shapefiles to PostGreSQL" button.  That was too easy!

I work in an all-ESRI shop and this is a nice break, especially because I'm a PostgreSQL fan.  Perhaps one day, I'll actually get to use it professionally!

Slow editing of GeoNets on SQL Server 2008

I wanted to use SQL2008's new geometry data type, but geometric networks  that use this data type result in extremely slow editing.  I add a new feature in ArcMap (9.3 SP1) and I sit around for 20 seconds waiting for ArcMap to acknowledge my existence.

The same geometric network using esri's data type works fine, and is really quick.  I'm not expecting geometry to be as fast as esri's, but it should be closer than what I'm experiencing.  Statistics and indexes on sql server 2008 are good to go--if I could just use something other than ESRI ArcStuff, I wouldn't be posting!

It is an ESRI issue with an open incident.  But frustrating nonetheless.  I'm still working through it--I'll post updates.