[Geoserver-users] sqlserver datastore wfs

Dear list

I have found some posts about sqlserver performance issues when doing wfs requests an large datasets.

Sqlserver chooses a non-optimal queryplan when doing a spatial query with sqlserver native paging.

Without native paging sqlserver is slow when performing non spatial requests

This happens when geoserver sends a query with a combination of “SELECT top xxx” and “SHAPE”.Filter(….).

This kind of query is slow because the queryplan decides not to use the spatial index.

Unfortunately it is not possible to specify a query hint [with(index(indexname))] because sqlserver throws an error when no spatial filter is specified.

· What is the status of this issue?

· Does anyone know a workaround for this problem?

Thanks

Bart Verbeeck

Afdeling Geodiensten - Dienst IT

T 09 276 14 78 | bart.verbeeck@anonymised.com | www.agiv.be

Dear list

I have found some posts about sqlserver performance issues when doing wfs requests an large datasets.

Sqlserver chooses a non-optimal queryplan when doing a spatial query with sqlserver native paging.

Without native paging sqlserver is slow when performing non spatial requests

This happens when geoserver sends a query with a combination of “SELECT top xxx” and “SHAPE”.Filter(….).

This kind of query is slow because the queryplan decides not to use the spatial index.

Unfortunately it is not possible to specify a query hint [with(index(indexname))] because sqlserver throws an error when no spatial filter is specified.

· What is the status of this issue?

· Does anyone know a workaround for this problem?

Thanks

Bart Verbeeck

Afdeling Geodiensten - Dienst IT

T 09 276 14 78 | bart.verbeeck@anonymised.com… | www.agiv.be

···

AGIV e-mail disclaimer: http://www.agiv.be/gis/organisatie/?artid=355

Hello, Bart.

Sorry about the lack of response. I was using Geoserver with SQL Server initially, but it performed poorly. On the other hand, Geoserver and PostGIS work really nicely together, so I now install PostGIS and Geoserver on the same server, and replicate my data to PostGIS. (This might not be what you wanted to hear.)

Regards,

David Collins

Geological Survey of NSW

···

On Mon, Jan 18, 2016 at 8:31 PM, Bart Verbeeck <Bart.Verbeeck@anonymised.com> wrote:

Dear list

I have found some posts about sqlserver performance issues when doing wfs requests an large datasets.

Sqlserver chooses a non-optimal queryplan when doing a spatial query with sqlserver native paging.

Without native paging sqlserver is slow when performing non spatial requests

This happens when geoserver sends a query with a combination of “SELECT top xxx” and “SHAPE”.Filter(….).

This kind of query is slow because the queryplan decides not to use the spatial index.

Unfortunately it is not possible to specify a query hint [with(index(indexname))] because sqlserver throws an error when no spatial filter is specified.

· What is the status of this issue?

· Does anyone know a workaround for this problem?

Thanks

Bart Verbeeck

Afdeling Geodiensten - Dienst IT

T 09 276 14 78 | bart.verbeeck@anonymised.com | www.agiv.be


AGIV e-mail disclaimer: http://www.agiv.be/gis/organisatie/?artid=355


Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140


Geoserver-users mailing list
Geoserver-users@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

On Mon, Jan 18, 2016 at 10:31 AM, Bart Verbeeck <Bart.Verbeeck@anonymised.com>
wrote:

Dear list

I have found some posts about sqlserver performance issues when doing wfs
requests an large datasets.

Sqlserver chooses a non-optimal queryplan when doing a spatial query with
sqlserver native paging.

Without native paging sqlserver is slow when performing non spatial
requests

This happens when geoserver sends a query with a combination of “SELECT
top xxx” and “SHAPE”.Filter(….).

This kind of query is slow because the queryplan decides not to use the
spatial index.

Unfortunately it is not possible to specify a query hint
[with(index(indexname))] because sqlserver throws an error when no spatial
filter is specified.

Did you use the spatial index forcing flag in the store configuration?

· What is the status of this issue?

Unknown.
Commercial databases data stores are normally worked on only on contract,
it's hard to convince anyone
to care/get excited for a commercial database in their own spare time.
You can look at the commercial support page to get someone look into the
issue for you http://geoserver.org/support/
Or you can just contribute changes yourself, everybody can participate, the
store is in GeoTools
and the rules to provide a code changes are here:
https://github.com/geotools/geotools/blob/master/CONTRIBUTING.md

It's probably not the answer you want (sorry about that!) but it's at least
a way forward.

Cheer
Andrea

--

GeoServer Professional Services from the experts! Visit
http://goo.gl/it488V for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via di Montramito 3/A
55054 Massarosa (LU)
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

*AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*

Le informazioni contenute in questo messaggio di posta elettronica e/o
nel/i file/s allegato/i sono da considerarsi strettamente riservate. Il
loro utilizzo è consentito esclusivamente al destinatario del messaggio,
per le finalità indicate nel messaggio stesso. Qualora riceviate questo
messaggio senza esserne il destinatario, Vi preghiamo cortesemente di
darcene notizia via e-mail e di procedere alla distruzione del messaggio
stesso, cancellandolo dal Vostro sistema. Conservare il messaggio stesso,
divulgarlo anche in parte, distribuirlo ad altri soggetti, copiarlo, od
utilizzarlo per finalità diverse, costituisce comportamento contrario ai
principi dettati dal D.Lgs. 196/2003.

The information in this message and/or attachments, is intended solely for
the attention and use of the named addressee(s) and may be confidential or
proprietary in nature or covered by the provisions of privacy act
(Legislative Decree June, 30 2003, no.196 - Italy's New Data Protection
Code).Any use not in accord with its purpose, any disclosure, reproduction,
copying, distribution, or either dissemination, either whole or partial, is
strictly forbidden except previous formal approval of the named
addressee(s). If you are not the intended recipient, please contact
immediately the sender by telephone, fax or e-mail and delete the
information in this message that has been received in error. The sender
does not give any warranty or accept liability as the content, accuracy or
completeness of sent messages and accepts no responsibility for changes
made after they were sent or for other risks which arise as a result of
e-mail transmission, viruses, etc.

-------------------------------------------------------