![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
hello! i am wanting to know if folks can share insights and comments regarding spatially enabling an OLTP database. There are some developers who are contemplating having this installed on our informix oltp database which seems to me like it may run into issues in regards to affecting performance of the database and the web application that runs on it, etc. Currently, the idea is to spatially enable the warehouse data that is a pull of information from the oltp system but they are looking into the idea of doing this directly within the oltp database at a possible future date. Thanks in advance! Tom _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#3
| |||
| |||
|
|
hello! i am wanting to know if folks can share insights and comments regarding spatially enabling an OLTP database. There are some developers who are contemplating having this installed on our informix oltp database which seems to me like it may run into issues in regards to affecting performance of the database and the web application that runs on it, etc. Currently, the idea is to spatially enable the warehouse data that is a pull of information from the oltp system but they are looking into the idea of doing this directly within the oltp database at a possible future date. Thanks in advance! Tom _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#4
| |||
| |||
|
#5
| |||
| |||
|
|
I may have not been clear on what some folks are looking at here . We have a separate warehouse arena (it is db2 actually) - while the OLTP system is not apart of the warehouse and runs on Informix with a web front end. What some here have suggested is spatially enabling the informix oltp system rather than doing so in the warehouse. my concern was that spatially enabling the oltp system would cause enough overhead to be detrimental to the performance of the oltp system. does that make sense? thanks again _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#6
| |||
| |||
|
#7
| |||
| |||
|
|
The regular spatial database will allow you to store spatial data in a vendor specific (closed) manner - generally as a BLOB (optianally using a middleware such as SDE) while afore mentioned spatial databases implement the open OGC standards: thus not locking you down to a specific desktop GIS or middleware database extension. |
#8
| |||
| |||
|
|
one more twist to this thread - what do you think of these two postings? 1) Microsoft SQL Server 2008 has been uniquely designed to support spatial data. Overview Microsoft SQL Server 2008 delivers comprehensive spatial support that enables organizations to seamlessly consume, use, and extend location- based data through spatial-enabled applications which ultimately helps end users make better decisions. http://www.microsoft.com/sqlserver/2...tial-data.aspx 2) http://spatialnews.geocomm.com/commu...phtml?id=22912 The idea of a "spatially enabled" database is seriously obsolete architecture. I don't blame the vendors who would like to codify this approach, since after all they are only trying to protect their aging products against more modern competition. But, if you look at what is possible with modern technology it's clear that there are many approaches that provide all of the same technical benefits with much greater performance. If you are working with modern GIS software you can work with very high speed with any enterprise class database. In fact, the last thing you want is to have a handful of trivial DBMS "spatial" hacks standing in the way of intense, scalable geoprocessing performance. The regular spatial database will allow you to store spatial data in a vendor specific (closed) manner - generally as a BLOB (optianally using a middleware such as SDE) while afore mentioned spatial databases implement the open OGC standards: thus not locking you down to a specific desktop GIS or middleware database extension. That's true, but the price you pay for using OGC is that it locks you down to an obsolete, slow and non-scalable architecture. The gain of going vendor-specific is often a hundred-fold or thousand-fold increase in performance, superior integration, dramatically expanded capabilities and reduced cost of ownership. A good example is the difference between Manifold's Enterprise Edition using standard Oracle (or SQL Server) as opposed to, say, an ESRI OGC client/middleware combination working with Oracle Spatial. If you have 100 users doing real geoprocessing with the OGC approach your performance will drop to unusuably slow levels. With Manifold, because it is a truly distributed and scalable solution, your geoprocessing performance with 100 users will be the same as with one user. Not only is Manifold 100 times faster, it is much less expensive, it provides many more capabilities and you have a better choice of DBMS vendors. _______________________________________________ Informix-list mailing list Informix-list (AT) iiug (DOT) org http://www.iiug.org/mailman/listinfo/informix-list |
#9
| |||
| |||
|
#10
| |||
| |||
|
|
From: tomcaml (AT) gmail (DOT) com Subject: Re: spatially enabled databases Date: Wed, 10 Feb 2010 12:28:50 -0800 To: informix-list (AT) iiug (DOT) org one more twist to this thread - what do you think of these two postings? 1) Microsoft SQL Server 2008 has been uniquely designed to support spatial data. Overview Microsoft SQL Server 2008 delivers comprehensive spatial support that enables organizations to seamlessly consume, use, and extend location- based data through spatial-enabled applications which ultimately helps end users make better decisions. http://www.microsoft.com/sqlserver/2...tial-data.aspx 2) http://spatialnews.geocomm.com/commu...phtml?id=22912 |
![]() |
| Thread Tools | |
| Display Modes | |
| |