Hello, after this Email is lying around for a few days like a hot potato, I'll try to answer a few questions. I do not have any experience with SQL Server I might add, however, somebody else may be able to fill this in. What I can offer is some knowledge, some experience and some opinion.
1 It is safe to add tables with no spatial column to geoserver. Yes. Things like reference tables for instance, but you need to allow for this when defining the datastore (tick the last tickbox 'geometryless tables'). With the other question 'empty tables' uuuhm why would you do that? 2 I do not know with SQL Server, but not with other DBs. 3 I do not know but it seems to me a bad idea. How do you want to style something like this? 4 Yes. At least they do with Oracle and ArcSDE 5 No geoserver will throw an error. 6 I do not know 7 java -server allows for a 64M permanent memory space. Geoserver has a lot of classes. It needs more, particularly if you have many layers and styles and plug-ins. So, java -XX:PermSize=96m -XX:MaxPermSize=128M. Something like that, there are other mailings on this list dealing with this problem. I do not know whether you have to use SQL Server or not, but it sounds to me like a database system I would not touch. It appears to be a very lenient system according to your description and one that allows bad geometry, different geometries etc. One advice: please, please clean up your data, no spikes, bowties, self-intersecting polygons etc. and any WMS will reward you with a better stability. Geoserver is rather patient with these things but it does not cater for everything. You would want a WMS to be fast, but it will either be fast or do a good exception handling. Esri is relatively stable and fast, but it is only so, because ArcSDE is so finicky and fussy with valid geometry. You wouldn't even get your data into ArcSDE. MapInfo has never managed to produce a stable WMS. That is not because they cannot program, but because MapInfo format accepts any spatial feature, however crooked. Geoserver tries to occupy some middle ground as it caters for a range of spatial formats. Please care about data quality and educate your data providers otherwise operating a WMS, will be a nightmare whatever you use. Cheers Christian ----- ____________________________ Dr Christian Maul Project Manager Information Services Branch Department of Sustainability and Environment Level13, Marland House, 570 Bourke Street Melbourne 3000 PO Box 500, East Melbourne Vic 3002 Telephone: +61-3-8636 2325 Telefax: +61-3-8636 2813 -- View this message in context: http://osgeo-org.1560.n6.nabble.com/Geoserver-2-1-3-2-2-some-problems-and-questions-tp5020078p5020809.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
