Latest Contributions by JimSmith

‎10-15-2014

Yes, the database server will change, we have to migrate all Geodatabases from SQL 2005 or 2008 to 2012 and this will require putting them on a new clustered environment.Thank you for suggesting the use of Python. Esri Support says: You can automate this using the arcpy.mapping python module. Refer to the following Web Help on the arcpy.mapping module as well as the arcpy mapping tutorial: http://resources.arcgis.com/en/help/main/10.2/index.html#/Updating_and_fixing_data_sources_with_arcpy_mapping/00s30000004p000000/ http://resources.arcgis.com/en/help/main/10.2/index.html#/Getting_started_with_arcpy_mapping_tutorial/00s30000006w000000/ this is a good start, we have an analyst working on it now. thanks!

‎10-09-2014

My organization is upgrading the ESRI environment to Desktop 10.2.2 (better late than wait for 10.3 - I guess) and upgrading all ArcSDE Geodatabases in coordination with this software upgrade. Users are almost all currently at 10.1. Desktop, with about 150 installations of Basic and Advanced. All installs are pointing at two enterprise-wide ArcSDE geodatabases that run on an MSSQL 2005 cluster. We are going to move the geodatabases to another MSSQL instance, 2012, and the procedure for moving and upgrading the databases themselves is straightforward. However we don't know what the impact of moving the data sources will be for 150+ staff who've got probably at least 10 ArcMap projects each pointing at the current geodatabase location. We know that just replacing the Database Connection file (.sde) with new ones set to the new database location, will not affect the data source already embedded in the .mxd file. We know that there is a "set data sources" dialog that lets you globally change a data source path within a project. This would be a manual process in which each user opens every .mxd and applies the changes. Maybe that's not so painful after all since they may be able to apply the changes on an as-needed basis. But given the number, locations, and skill levels of the entire user community, I'm looking for a way to minimize the time and effort it takes to get the new data sources working for them. Is there any other way to automate or streamline the task of updating potentially hundreds of data source paths for many users? If automation is not really an option what is the best way to perform this type of user environment change? Any suggestions or experiences you would like to share? thanks!

‎09-30-2014

Correction to my post: an explanation of multiple editors using move to base (MTB) option is in the ESRI course workbook, Lesson 10, and there on page 10-8 is the very same warning message: "Your edits could not be saved because the target version has been updated since you started editing. These edits have been merged into your edit session. Review the changes and save again." This is because when using the MTB option the edits are no longer isolated after they have been saved... the target version, Default, has been updated... so, when two users change Default at the same time, the second editor to save must do an implicit reconcile (first save) and then an implicit post (second save after message) in order to move the changes to the base tables. Above responses are both correct in identifying the cause (Robert) and the fix (Asrujit). We have multiple editors and update scripts applying changes to Default version. We have asked the users of this Geodatabase to set versioning to "Automatically save changes..."

‎08-11-2014

Environment: ArcGIS 10.1, ArcSDE Geodatabase 10.1, SQL Server 2008R2 User is editing a feature class registered as versioned with move to base option. She sometimes gets the following message when trying to save edits: "Your edits could not be saved because the target version has been updated since you started editing. These edits have been merged into your edit session. Review the changes and save again." As far as we know she is the only editor at that time. The Geodatabase is used as a project workspace for geoprocessing data by 6-10 users. That includes the possibility that other users are creating new feature classes, altering table schema in existing feature classes, or performing bulk load operations - in default - while the user is editing. Can any of the other users' actions result in changes to default and cause the message? I think the short answer is "use fully versioned workflows" but need clarification on what constitutes an "update" to default version - it's not in the training book. Thanks!

‎05-14-2013

There was a domain name change, but the blog post is still available: http://geodatabase.net/wp/sql-server-2008-spatial-indexes-and-arcsde-9-3/ The content of that blog post, and this forum discussion, is pretty good, but it all is nearly 2 1/2 years old. ArcSDE has changed some and SQL Server has had lots of improvements to its spatial support. If you are truly running SQL Server 2008 with no service packs and ArcSDE 9.3/9.3.1, I think there is likely a larger issue that needs to be discussed more than tuning spatial indexes. Good luck! Thanks for the link and feedback. For this issue, both ArcGIS and Geodatabase are 10.1 sp1, MSSQL is 2008R2. We imported a parcel base feature class of ~300,000 polygons, stored in sde_binary, and it performs just fine, as it always has since the days of MSSQL 2000 and 9.something ... but an exact copy of it with geometry storage, display and query performance is unacceptable, almost shapefile slow. The layer envelope is not the issue. I can't find any discussion on the support forums etc. or guidance in online help. Any suggestions? Thanks!

‎05-09-2013

That did it. Draw times are now on par with sdebinary. Thanks! Hi, I *really* need to know the content of that blog post, which is no longer available. Can you provide me with the fix for slow draw times with SQL 2008 geometry on large sets of features? thanks!

‎02-02-2012

The answer to my question, are SQL Server 2008 R2 and ArcSDE 9.2 compatible, is yes. We had to make one change to the dbtune table: set the DEFAULTS keyword UNICODE_STRING to FALSE. Our old MO app would not recognize Unicode field values. If you need to preserve a 9.2 geodatbase instance you will need to also keep one ArcSDE application server at 9.2; ArcSDE 9.3 or 10 cannot manage older versions of the geodatabase.

‎09-27-2011

Hello Vince, this is off topic and a little late, but I am looking for verification on compatibility between ArcSDE server and database versions. We have a need to preserve a SQL Server Geodatabase instance at version 9.2 but we must also upgrade the ArcSDE application server to 9.3.1 (don't ask why we can't go to 10 🙂 I tried to create a service on the 9.3.1 side and connect to the 9.2 database (which sits on a separate database server). The service fails to start and logs the message Previous SDE Server Release 9.2.0 is not compatible with the current Release 9.3.1. The users who need this gdb must use a service, their app does not do direct connects. Is this it, are we done and forced to remain at 9.2? Is there another thread you can point me to? Thanks!

‎03-29-2011

We have a user group that needs to keep a legacy application alive while it is being replaced. The legacy app, a MapObjects 2.x thing, is not compatible with geodatabase versions later than 9.2 (we tested it with 9.3 and it does not recognize certain features). The app requires a service connection via ArcSDE server because it is not an ArcMap extension, it is standalone. IT wants to migrate the server to virtual environment and also use SQL Server 2008, so we have built and tested a VM with ArcSDE 9.2 SP6 and SQL Server 2008. It seems to work. Now IT wants to upgrade this virtual server to SQL 2008 R2 before we cut over the users. Is there anyone who can give me some feedback on whether this will work? Thanks.

Online Status	Offline
Date Last Visited	‎11-11-2020 02:23 AM

My Ideas

Latest Contributions by JimSmith

Re: When moving ArcSDE geodatabases, how to update many .mxd data sources?

When moving ArcSDE geodatabases, how to update many .mxd data sources?

Re: What is updating geodatabase default version?

What is updating geodatabase default version?

Re: Spatial Index Performance: SQL 2008 vs ArcSDE

Re: Spatial Index Performance: SQL 2008 vs ArcSDE

Re: SQL Server 2008 R2 and ArcSDE 9.2?

Re: Problem writing to SDE using ArcObjects API -Error- ORA-01036: illegal variable n

SQL Server 2008 R2 and ArcSDE 9.2?

What is updating geodatabase default version?