<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Support for SQL Server</title>
	<atom:link href="http://blog.geoserver.org/2008/11/10/146/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.geoserver.org/2008/11/10/146/</link>
	<description>Everything GeoServer, and a little more</description>
	<lastBuildDate>Sat, 24 Dec 2011 16:57:18 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: Justin Deoliveira</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-52867</link>
		<dc:creator>Justin Deoliveira</dc:creator>
		<pubDate>Wed, 23 Sep 2009 18:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-52867</guid>
		<description>@ 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.</description>
		<content:encoded><![CDATA[<p>@ Sjoerd:</p>
<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sjoerd</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-52649</link>
		<dc:creator>Sjoerd</dc:creator>
		<pubDate>Tue, 22 Sep 2009 19:52:02 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-52649</guid>
		<description>I&#039;ve tested this with a &#039;simple&#039; dataset with approx 5 million points. Results are a bit disappointing because the performance is very poor (&gt; 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(&#039;POLYGON ((10 50, 19 59, 19 59,19 59,10 50))&#039;, 28992)) = 1

are performed.

I only see queries that contain:

select a,b,c CAST(&quot;the_geom&quot;.STSrid as VARCHAR) + &#039;:&#039; &quot;the_geom&quot;.STasText() as &quot;the_geom&quot; FROM MyDB


Perhaps i&#039;m doing something wrong?</description>
		<content:encoded><![CDATA[<p>I&#8217;ve tested this with a &#8216;simple&#8217; dataset with approx 5 million points. Results are a bit disappointing because the performance is very poor (&gt; 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.<br />
No spatial queries like:</p>
<p>select * from MyDB where the_geom.STIntersects(geometry::STGeomFromText(&#8216;POLYGON ((10 50, 19 59, 19 59,19 59,10 50))&#8217;, 28992)) = 1</p>
<p>are performed.</p>
<p>I only see queries that contain:</p>
<p>select a,b,c CAST(&#8220;the_geom&#8221;.STSrid as VARCHAR) + &#8216;:&#8217; &#8220;the_geom&#8221;.STasText() as &#8220;the_geom&#8221; FROM MyDB</p>
<p>Perhaps i&#8217;m doing something wrong?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debe</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-52604</link>
		<dc:creator>Debe</dc:creator>
		<pubDate>Tue, 22 Sep 2009 12:38:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-52604</guid>
		<description>Does the extension support wfs-t.</description>
		<content:encoded><![CDATA[<p>Does the extension support wfs-t.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders blogger in direct mail</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-41559</link>
		<dc:creator>Anders blogger in direct mail</dc:creator>
		<pubDate>Sun, 05 Jul 2009 15:04:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-41559</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Support for SQL Server GeoServer Blog &#124; debt settlement program</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-39272</link>
		<dc:creator>Support for SQL Server GeoServer Blog &#124; debt settlement program</dc:creator>
		<pubDate>Mon, 15 Jun 2009 16:58:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-39272</guid>
		<description>[...] 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&#160;  &#124;&#160; Bury &#124;&#160;    News &#124; Support for SQL Server GeoServer Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Support for SQL Server GeoServer Blog   Posted by root 12 minutes ago (<a href="http://blog.geoserver.org" rel="nofollow">http://blog.geoserver.org</a>)        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&nbsp;  |&nbsp; Bury |&nbsp;    News | Support for SQL Server GeoServer Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Support for SQL Server GeoServer Blog &#124; Paid Surveys</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-37870</link>
		<dc:creator>Support for SQL Server GeoServer Blog &#124; Paid Surveys</dc:creator>
		<pubDate>Tue, 02 Jun 2009 08:24:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-37870</guid>
		<description>[...] 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&#160;  &#124;&#160; Bury &#124;&#160;    News &#124; Support for SQL Server GeoServer Blog [...]</description>
		<content:encoded><![CDATA[<p>[...] Support for SQL Server GeoServer Blog   Posted by root 3 hours ago (<a href="http://blog.geoserver.org" rel="nofollow">http://blog.geoserver.org</a>)        Post a comment your email is never shared required fields are marked geoserver blog hosted by opengeo powered by wordpress log in        Discuss&nbsp;  |&nbsp; Bury |&nbsp;    News | Support for SQL Server GeoServer Blog [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: huskz</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-36343</link>
		<dc:creator>huskz</dc:creator>
		<pubDate>Mon, 11 May 2009 16:46:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-36343</guid>
		<description>i have same problem as keith. I am using geoserver 1.7.4 and sql server 2008 express.</description>
		<content:encoded><![CDATA[<p>i have same problem as keith. I am using geoserver 1.7.4 and sql server 2008 express.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: keith</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-35769</link>
		<dc:creator>keith</dc:creator>
		<pubDate>Wed, 29 Apr 2009 19:16:10 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-35769</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Justin Deoliveira</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-31650</link>
		<dc:creator>Justin Deoliveira</dc:creator>
		<pubDate>Thu, 26 Mar 2009 15:52:11 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-31650</guid>
		<description>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.</description>
		<content:encoded><![CDATA[<p>Rob:</p>
<p>What was released for the sql server driver is pretty much as basic as it gets. No WKB, no spatial index support, etc&#8230; 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.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rob</title>
		<link>http://blog.geoserver.org/2008/11/10/146/comment-page-1/#comment-31592</link>
		<dc:creator>Rob</dc:creator>
		<pubDate>Thu, 26 Mar 2009 05:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://blog.geoserver.org/?p=146#comment-31592</guid>
		<description>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</description>
		<content:encoded><![CDATA[<p>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?</p>
<p>Rob</p>
]]></content:encoded>
	</item>
</channel>
</rss>

