We are wondering how to improve the performance in editing SQL feature class of 250,000 records that contains 250,000 records. It appears that compress, rebuild and analyze don’t help that much in enhancing the editing considerably. Editing is really slow at the moment!
We'll need some additional information to better understand the factors that could potentially be affecting the performance you're witnessing.
- What version of SQL Server are you using?
- What is your ArcGIS Desktop/Enterprise geodatabase version(s)?
- Is the client machine that you are making these edits on located on the same machine as the database server?
- What type of geometry are your feature classes stored in?
- Is the performance issue strictly limited to editing operations? Is panning/zooming slow? GP tool performance?
- Have you always witnessed latency or is this something that has recently occurred?
- Have any architectural changes occurred recently? DBMS Upgrade? Moving data to a new server?
- Are your feature classes registered as versioned?
- How often do you run geodatabase maintenance?
- Is performance only witnessed on this single feature class or is it database-wide?
Sounds like you might need to do some tuning on the back end of your SQL database, if you're using SQL express remember there's only a 10gb per database max and even less for earlier versions. Some of the questions Quinn asked would be helpful to pin point the problem.
Thanks all for the answers.
Thank you for your answer, kindly see the following:
So, what might be the issue here?
Thanks in advance