Support for SQL Server

The GeoServer team is happy to announce an extension for Microsoft SQL Server, currently available as a nightly build. Instructions for getting the extension up and running are available on the wiki.

At this point the extension is still quite young and is missing some key features like spatial indexing and support for well known binary. By trying it out and providing us with feedback you can help drive development of these features.

The extension is based on the recent re-architecture in GeoTools for database backed data stores. Code named “JDBC Next Generation”, it provides a framework for building new data store implementations quickly and robustly. Also based on this architecture are soon to come improved extensions for MySQL, Oracle, and DB2. A new extension for SpatiaLite is also in the works.

Download the SQL Server extension and try it out. We are very eager to here any feedback on the mailing list. You can also help us make it better by reporting any issues in our bug tracker.

14 Comments

  1. Mike Pumphrey
    Posted November 19, 2008 at 11:19 am | Permalink

    Just wanted to point out that this is specifically for SQL Server 2008, as this was the version where spatial support was added. So, for those using SQL Server 2000 or 2005, time to upgrade!

  2. Jasun Chang
    Posted December 29, 2008 at 10:06 pm | Permalink

    I am a new kid in the block. Is there a GeoJson Datastore extension for Geoserver? Thanks.

    Jasun

  3. Posted December 31, 2008 at 1:41 pm | Permalink

    Jasun:

    There is no datastore extension for serving geojson sitting in a file on disk (or some other source). Only an output format for wfs to serve up data as geojson.

  4. Jasun Chang
    Posted December 31, 2008 at 10:47 pm | Permalink

    Justin,

    Thanks for the reply. Then, does geoserver provide a direct method or web service to create a new feature layer (such as buffer or intersection) without relying using command level GDAL commands or POSTGIS commands?

    Thanks.

    Jasun

  5. Posted January 1, 2009 at 9:39 pm | Permalink

    Jason,

    Not really. Currently we are working on a Web Processing Service (WPS) implementation in GeoServer, but it is still in the experimental stages.

  6. Jasun Chang
    Posted January 2, 2009 at 10:31 pm | Permalink

    Justin,

    Thanks. Any time frame for the official release for the WPS. 2 months or 6 months? Any other suggestions?

    Your help is really appreciated.

    Jasun

  7. Rob
    Posted March 26, 2009 at 12:25 am | Permalink

    Is there going to be support added for WKB and spatial indexing with the SQL Server 2008 datasource (or has this already been implemented)? SQL server has the .STAsBinary ( ) function call on the geometry type. We have been running into serious scalability problems with large vector datasets with geoserver and am wondering if it has do with the lack of the datasources ability to utilize WKB and spatial indexes?

    Rob

  8. Posted March 26, 2009 at 10:52 am | Permalink

    Rob:

    What was released for the sql server driver is pretty much as basic as it gets. No WKB, no spatial index support, etc… so I am not all that surprised you are having scalability issues. What is needed is a sponsor for this work. I suggest you send mail to the users list. If enough users are having the same issue it is more likely something will get done about it.

  9. keith
    Posted April 29, 2009 at 2:16 pm | Permalink

    It seems to me the SQL Server extension is not working when creating FeatureType. It cannot populate SRS, Max/Min Long, Max/Min Lat. After entering them, cannot see map.

  10. huskz
    Posted May 11, 2009 at 11:46 am | Permalink

    i have same problem as keith. I am using geoserver 1.7.4 and sql server 2008 express.

  11. Posted July 5, 2009 at 10:04 am | Permalink

    I have with great interest read your blog. Finally meeting someone who in simple sentences can point out the essentials needed to make a good DM campaign. This however cannot stand alone; it must be just a part of the total marketing, integrated in the complex world of profitable online marketing. Today we all talk about being effective, targeted and to get optimal results out of the investments in the Internet Market Place and that is not easy; do not tell your prospects that. I think it is often overlooked that DM campaigns must be sharply targeted shoot with rifles not with pellets hoping to hit something. Many clients are impressed when they are told that a DM campaign with 10.000 pellets can result in a high response but what does it help if 50 % or more are useless and the real conversion rate is only 10 %. Does that give a good ROI, no. Better use the principle target narrowly and make more hits.

  12. Debe
    Posted September 22, 2009 at 7:38 am | Permalink

    Does the extension support wfs-t.

  13. Sjoerd
    Posted September 22, 2009 at 2:52 pm | Permalink

    I’ve tested this with a ‘simple’ dataset with approx 5 million points. Results are a bit disappointing because the performance is very poor (> 60 seconds for a single WFS request). In the SQL 2008 performance monitor GeoServer seems to query the complete DB and does the bbox handling itself.
    No spatial queries like:

    select * from MyDB where the_geom.STIntersects(geometry::STGeomFromText(‘POLYGON ((10 50, 19 59, 19 59,19 59,10 50))’, 28992)) = 1

    are performed.

    I only see queries that contain:

    select a,b,c CAST(“the_geom”.STSrid as VARCHAR) + ‘:’ “the_geom”.STasText() as “the_geom” FROM MyDB

    Perhaps i’m doing something wrong?

  14. Posted September 23, 2009 at 1:42 pm | Permalink

    @ Sjoerd:

    Nope, nothing wrong. The implementation that is there needs to be further developed to use the spatial index in such queries. Its very doable, but just requires a) someone to fund it or b) a developer to show up and implement it.

5 Trackbacks

  1. By Suporte ao SQL Server no GeoServer » Fernando Quadro on November 13, 2008 at 10:42 am

    […] Fonte: Blog do GeoServer […]

  2. By Links (01.12.2008) « Geospatial Web on December 1, 2008 at 6:43 am

    […] Support for SQL Server. GeoServer bietet neuerdings auch eine Extension zur Anbindung von Microsoft SQL Server. […]

  3. By GeoServer 1.7.1 Released - GeoServer Blog on December 9, 2008 at 11:56 am

    […] just improved Google Earth support.  GeoServer now has an official SQL Server extension (described previously). In addition, there is a new and improved Oracle extension which provides better performance and […]

  4. […] Support for SQL Server GeoServer Blog Posted by root 3 hours ago (http://blog.geoserver.org) Post a comment your email is never shared required fields are marked geoserver blog hosted by opengeo powered by wordpress log in Discuss  |  Bury |  News | Support for SQL Server GeoServer Blog […]

  5. […] Support for SQL Server GeoServer Blog Posted by root 12 minutes ago (http://blog.geoserver.org) Post a comment or leave a trackback blog hosted by opengeo powered by wordpress log in discuss bury news support for sql server geoserver blog Discuss  |  Bury |  News | Support for SQL Server GeoServer Blog […]

Download GeoServer