Hi all, Thought you might be interested in our experience. We have been managing an enterprise geodatabase (Oracle SDE) since SDE v3.0 which has grown to cater for 9 Queensland (Australia) state government departments with > 2000 datasets. As a result of relacing the database hardware in 2014 we undertook a complete redesign of the management structure within the DB. Our original plan was to use multiple SDE schemas within a 'parent' SDE but there were several issues which made this unacceptable in our situation. We then considered multiple databases with there own SDE however the number of DB's required meant there would be resource issues on the DB server (even though it is an 1/8th rack Exadata). To give you a feel for the size of some of these datasets, the Queensland Cadastre and drainage datasets each contain > 3 million records. Where we ended up was: A read only query SDE database A read/write update SDE database (with replication to the query database through python/manual processes) A read/write application SDE database (provides r/w access to web based applications) A read/write imagery SDE database (contains the mosaic datasets for all of our georeferenced imagery and elevation models) We use schema 'owners' to identify which department/group has responsibility for the datasets and roles (viewer & editor) for each schema as well as a general 'viewer' role to manage the datasets. All of our web services run off the query DB and are published using AGS to the DMZ using an F5 gateway and token security. Have there been issues? Plenty, but the major one has been providing an enterprise search mechanism which makes it easy for people to find what they are chasing. Even though we employ a naming convention (which not everyone follows) and require fairly strict metadata (which again not everyone follows) it is fairly daunting to search through >2000 datasets. We attempted to use the enterprise search functionality of AGS however this bypasses our security model and means anyone using the search connects to the DB as the 'search user' which is not desirable in our situation. We are now working towards using GeoPortal to provide a search mechanism. Once we are happy with the standard of the metadata we may integrate these as secure records in our enterprise GeoPortal (http://qldspatial.information.qld.gov.au/catalogue/custom/index.page ). Hope this is of some help and we are more than happy to share our experiences. Greg
... View more
