I don't intend to move data from one server to another. I shouldn't have to, if there is an Oracle DB that have spatial table right? I can just let any MapGuide Server access the Oracle DB, read the spatial table and serve/publish that spatial table as an layers/maps/etcs.
So really there is no need to create an .mgp package right? If I do decide to create .mgp package of the Oracle DB, then could I just choose one spatial table to create a package, just for that table? Or do I have to create a package of the whole Oracle DB with all the spatial tables in it? that wouldn't be good if the Oracle DB instance is really big, like more than 30gb with all those spatial tables in it. -- View this message in context: http://osgeo-org.1560.x6.nabble.com/mgp-with-Feature-Source-Oracle-tp5319793p5319803.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org https://lists.osgeo.org/mailman/listinfo/mapguide-users
