Hi:
We have a sde 10.0 running on DB2. There are about 4000 featureclasses in the sde, including point,polyline,polygon,annotation and mosaic dataset. Some annotation featureclass has 2 or 3 million records. We use direct connection to DB2. Now we have a problem.
When we double click the database connection in ArcCatlog, it needs more than 2 minutes to list all the featuredatasets. During these two minutes, ArcCatlog has no response. All the employee using the ArcCatlog are complaining. Besides, when we need to add data in ArcMap, it will take the same time which is several minutes to add the selected featureclass to the ArcMap. After we add the featureclass to the arcmap, the drawing speed is OK.
What is ArcCatlog doing when it make the connection the database? Does anyone have experience such kind of situation before? Is it possible to store thousands of featureclass in the ArcSDE? Should we modify some configuration parameter in the DB2?
Any comments would be appreciated. Thank you .
We have a sde 10.0 running on DB2. There are about 4000 featureclasses in the sde, including point,polyline,polygon,annotation and mosaic dataset. Some annotation featureclass has 2 or 3 million records. We use direct connection to DB2. Now we have a problem.
When we double click the database connection in ArcCatlog, it needs more than 2 minutes to list all the featuredatasets. During these two minutes, ArcCatlog has no response. All the employee using the ArcCatlog are complaining. Besides, when we need to add data in ArcMap, it will take the same time which is several minutes to add the selected featureclass to the ArcMap. After we add the featureclass to the arcmap, the drawing speed is OK.
What is ArcCatlog doing when it make the connection the database? Does anyone have experience such kind of situation before? Is it possible to store thousands of featureclass in the ArcSDE? Should we modify some configuration parameter in the DB2?
Any comments would be appreciated. Thank you .
should NEVER, EVER own spatial data -- Best practice it to create at least one,
usually several, owners, and additional accounts for data users. The SDE user
password should be closely held to prevent geodatabase corruption.
Feature datasets exist for cooperative editing. If you're not editing these feature
classes together (as in pipes and values), then placing them inside feature datasets
slows down access (at connect time) and causes locking issues that will haunt you.
You can use owners and table naming to organize feature classes without falling
into the trap of using feature datasets as "folders".
You should not tamper with the indexes on SDE metadata tables. They already
have all the indexes they need -- adding others will just cause difficulty at upgrade.
- V