I am opening this open question topic because I am at a loss and dont have a good enough understanding of all the underlying operations going on 'under the hood' of Windows/Arcgis.
Before you read all the background below, these are my general questions which I hope the collective expertise and knowledge of this community can help with.
We have a central database (SDE on Windows Server 2008 R2 that contains most data on a national level) and a local (physical server) that is dedicated for geodata within each regional office. Certain datasets (large raster datasets, DEMs) are divided on a national level and also stored on the local server in the regional office.The infrastructure is set up by IT. Geodata is only a small part of this, so the geodata considerations do not always take priority with the entirety of the IT system (i.e. turning off opportunistic locking is not an option).
I have done some testing regarding performance of fgdb's vs shapefiles, network vs local drive, and in our current environment, the file geodatabases are appaling in performance.
Here are some tests I ran:
5 point featureclass datasets with 10 points each.
Due to our large organization and legal requirements, working on the local computer drive should be avoided due to lack of backup. In theory, all geodatawork should be done on the geodata network drive (local in-house server). When we upgrade to ArcGIS 10.3, with the easy option of 'let this be my home directory for this MXD' option, I would very much like to use the filegeodatabases to help keep all data organised, as there are several new MXD per week with plenty of scratch data floating around everywhere. However, with the performance issues that I have found, It feels we will still be stuck with shapefiles and a hard-to-keep-organized data environment.
I appreciate you time and expertise! thank you for reading this, I hope you can help with input.
أكثر...
Before you read all the background below, these are my general questions which I hope the collective expertise and knowledge of this community can help with.
- How to best use fgdb's on networks (best practice)?
- What is the root cause of fgdb performance issues how to avoid it?
We have a central database (SDE on Windows Server 2008 R2 that contains most data on a national level) and a local (physical server) that is dedicated for geodata within each regional office. Certain datasets (large raster datasets, DEMs) are divided on a national level and also stored on the local server in the regional office.The infrastructure is set up by IT. Geodata is only a small part of this, so the geodata considerations do not always take priority with the entirety of the IT system (i.e. turning off opportunistic locking is not an option).
I have done some testing regarding performance of fgdb's vs shapefiles, network vs local drive, and in our current environment, the file geodatabases are appaling in performance.
Here are some tests I ran:
5 point featureclass datasets with 10 points each.
- export from fgdb to fgdb on my local computer drive: 4 seconds
- export from fgdb to fgdb on network drive: 298 seconds
- export from .shp to fgdb on network drive: 225 seconds
- export from fgdb to .shp on network drive: 60 seconds
Due to our large organization and legal requirements, working on the local computer drive should be avoided due to lack of backup. In theory, all geodatawork should be done on the geodata network drive (local in-house server). When we upgrade to ArcGIS 10.3, with the easy option of 'let this be my home directory for this MXD' option, I would very much like to use the filegeodatabases to help keep all data organised, as there are several new MXD per week with plenty of scratch data floating around everywhere. However, with the performance issues that I have found, It feels we will still be stuck with shapefiles and a hard-to-keep-organized data environment.
I appreciate you time and expertise! thank you for reading this, I hope you can help with input.
أكثر...