Hi Chris and Justin,
I've chatted with the client...they're relatively small so the OpenGeo Professional edition is a huge pill to swallow. Perhaps unrealistic. They do, however, have database programmers on staff who might be able to do some development. I'm not sure yet of their skill set, but I'm thinking we might be able to arrange for some bug fixes on your end (under contract) and some code development on our end.
It's early stages yet, but I'd like to get some idea of what is involved in bringing this from proof of concept to a working datastore. Can we draw parallels with the Oracle datastore development in terms of what might be expected (types of problems, hours spent, etc)?
Thanks for the continued help.
Damian
Chris Holmes wrote:
Justin may sound in with more information, but I think you'll start seeing performance degradation once you get in to over 200,000 points.
If they're going to be using sql server in production I'd highly recommend getting them set up with an OpenGeo Suite Professional edition. See http://opengeo.org/products/suite/matrix/
We'd do unlimited bug fixes, and there would be enough hours to do spatial index support. We probably will sorta get screwed, which means it's a great deal for your client, because we completely commit to making it work perfectly. We had a client do the same with Oracle NG - we had to do a bunch of free bug fixes. But we're psyched to see things better supported, so it's ok if we take a bit of a loss.
Justin has done a great job on the SQL Server datastore, but we're waiting on a solid client before we give him more time to make it awesome.
best regards,
C
Damian Bradley wrote:
Hi there,
A potential client of mine has an SQL Server 2008, I was reading that it doesn't support a spatial index. What effect does this have on performance, back-end or end-user experience?
Thanks,
Damian
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Hi Damian,
All in all the work to bring sql server up to quality is a couple of weeks. However that estimate would be for somone who already is familiar with the geotools code base, and the datastore architecture. The geotools learning curve is unfortunately quite steep to the time getting set up is not to be underestimated.
That said the developers on the project will be happy to point you in the right direction. The first step in getting set up would be to checkout the geotools code from svn and get it built with maven. If you can do this (many people seem to fail at this step) you are looking good :). From there I can point you in the right direction.
-Justin
Damian Bradley wrote:
Hi Chris and Justin,
I've chatted with the client...they're relatively small so the OpenGeo Professional edition is a huge pill to swallow. Perhaps unrealistic. They do, however, have database programmers on staff who might be able to do some development. I'm not sure yet of their skill set, but I'm thinking we might be able to arrange for some bug fixes on your end (under contract) and some code development on our end.
It's early stages yet, but I'd like to get some idea of what is involved in bringing this from proof of concept to a working datastore. Can we draw parallels with the Oracle datastore development in terms of what might be expected (types of problems, hours spent, etc)?
Thanks for the continued help.
Damian
Chris Holmes wrote:
Justin may sound in with more information, but I think you'll start seeing performance degradation once you get in to over 200,000 points.
If they're going to be using sql server in production I'd highly recommend getting them set up with an OpenGeo Suite Professional edition. See http://opengeo.org/products/suite/matrix/
We'd do unlimited bug fixes, and there would be enough hours to do spatial index support. We probably will sorta get screwed, which means it's a great deal for your client, because we completely commit to making it work perfectly. We had a client do the same with Oracle NG - we had to do a bunch of free bug fixes. But we're psyched to see things better supported, so it's ok if we take a bit of a loss.
Justin has done a great job on the SQL Server datastore, but we're waiting on a solid client before we give him more time to make it awesome.
best regards,
C
Damian Bradley wrote:
Hi there,
A potential client of mine has an SQL Server 2008, I was reading that it doesn't support a spatial index. What effect does this have on performance, back-end or end-user experience?
Thanks,
Damian
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi Damian,
All in all the work to bring sql server up to quality is a couple of weeks. However that estimate would be for somone who already is familiar with the geotools code base, and the datastore architecture. The geotools learning curve is unfortunately quite steep to the time getting set up is not to be underestimated.
That said the developers on the project will be happy to point you in the right direction. The first step in getting set up would be to checkout the geotools code from svn and get it built with maven. If you can do this (many people seem to fail at this step) you are looking good :). From there I can point you in the right direction.
Btw, the GT2 developer guide provides details on how to get started with
svn, maven and Eclipse, see just "Introduction" and "Building".
If you use Netbeans there are some notes in the "Tools" section
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.
Andrea Aime ha scritto:
Justin Deoliveira ha scritto:
Hi Damian,
All in all the work to bring sql server up to quality is a couple of weeks. However that estimate would be for somone who already is familiar with the geotools code base, and the datastore architecture. The geotools learning curve is unfortunately quite steep to the time getting set up is not to be underestimated.
That said the developers on the project will be happy to point you in the right direction. The first step in getting set up would be to checkout the geotools code from svn and get it built with maven. If you can do this (many people seem to fail at this step) you are looking good :). From there I can point you in the right direction.
Btw, the GT2 developer guide provides details on how to get started with
svn, maven and Eclipse, see just "Introduction" and "Building".
If you use Netbeans there are some notes in the "Tools" section
Ah hem... I started writing the mail just to provide this link.. which I've then forgot to add:
http://docs.codehaus.org/display/GEOT/Home
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.