|
POST
|
Jacob Boyle, I have a testing environment with an editing sde gdb and a child file gdb. The process seems pretty straight-forward for syncing changes, and updating schemas. However, I removed a field from a feature class in my editing gdb and the field still remains in the child gdb after running the export->compare->import schema tools. I also added a domain and assigned the domain in the production gdb. The domain schema change is reflected in the child gdb. I'm wondering why the field that was removed in the editing fc still remains in the child fc? Does removing a field have to be done manually?
... View more
01-22-2016
09:40 AM
|
0
|
7
|
3526
|
|
POST
|
Jacob Boyle, Can replicas be overwritten or do they need to be unregistered from both gdbs? Thanks for help!!!
... View more
01-22-2016
07:52 AM
|
0
|
9
|
3526
|
|
POST
|
Jacob Boyle If schema were to change, do you need to delete / unregister the replica and then re-create it? I guess I'm wondering when that is necessary? Would adding a feature class or field in the production sde gdb be brought over by running the export schema -> compare schemas -> import schemas?
... View more
01-22-2016
06:09 AM
|
0
|
11
|
3526
|
|
POST
|
Joe Sapletal, That is very interesting!...and something that hadn't crossed my mind. Providing them themed layer files will not only avoid them having to search for data, but will take care of 'standardizing' symbology and labeling. You could even go so far as to create a python add-in and have buttons or a pick list that would load in the themes for users without them having to navigate a directory.
... View more
01-21-2016
10:04 AM
|
1
|
0
|
3083
|
|
POST
|
Jacob Boyle, Thanks for the responses, that does help! Say I wanted to script a routine to run daily, or on a regular interval to sync the parent gdb with the child gdb in a 1-way replica scenario. Would the steps below be realistic...?...or is there a 'better' or more realistic approach? 1) Reconcile and post edits in parent sde gdb to DEFAULT version 2) Export Replica Schema -> Compare Replica Schema -> Import Replica Changes --- this would be to keep schemas the same between the two gdb 3) Synchronize Changes
... View more
01-21-2016
08:34 AM
|
0
|
0
|
3526
|
|
POST
|
This is my first go around with gdb replication and am looking to create a 1-way replica from a sde gdb to either another sde gdb or a file gdb. I was hoping to get an idea of the best practices and workflows for keeping the two gdbs in sync? My assumption is you start with the Create Replica tool in order to replica data from parent to child, is that right? After that is done, I have a few questions about workflow and best practices... 1) How do you add a feature class to the child gdb after the replication process is in effect? 2) If a feature class is deleted from the parent gdb, how do you delete the feature class in the child?...do you simply delete it through ArcCatalog? 3) If a field is added or removed in a feature class within the parent gdb, how do you send that change to the child gdb?...can it be automated or is it manual? 4) If a domain is added / altered / removed, how do you send those changes to the child?...can it be automated or is it manual? 5) What is a good 'routing' for syncing changes? Do you first reconcile and post edits in the parent gdb, then sync changes? Should some processes, like comparing schema be done first before syncing changes? I'm looking to get an idea of what workflows others use that have been successful, easy to manage, and keeps your data in sync. Thanks!
... View more
01-21-2016
08:09 AM
|
4
|
18
|
10499
|
|
POST
|
Vince Angelo, That's interesting about the datasets. Would you recommend not using datasets unless complex functions (i.e. topology, geometric networks) are needed?
... View more
01-19-2016
01:26 PM
|
0
|
9
|
2421
|
|
POST
|
Dan Patterson - haha, unfortunately we've been bitten by the backup validity as well
... View more
01-19-2016
09:06 AM
|
0
|
0
|
2843
|
|
POST
|
James Crandall, We have thought about this approach as well, and already kind of have it implemented in our 1 production sde gdb. We have 'Publish' datasets that are non-versioned and read-only. These are mainly datasets that do not change over time or are feature classes that are produced from other business systems through views. Our web side of things is a replicated file gdb on our app server. This is meant to separate our web environment from our production environment and has dramatically reduced the number of connections to our production sde gdb.
... View more
01-19-2016
08:49 AM
|
2
|
0
|
2843
|
|
POST
|
Joe Borgione, Did you end up splitting up your multi-version one gdb? If so, do you find performance advantages?...administrative advantages? ...and yes, 45 datasets containing 278 feature classes.
... View more
01-19-2016
08:46 AM
|
0
|
7
|
5024
|
|
POST
|
Dan Patterson, Do you mean database corruption, or something similar? If so, I would think having several smaller gdbs would be advantageous, not a disadvantage. If 1 gdb became corrupt, it's not a total loss of data. In terms of backups, our Sql backups are automated by our DBA, so, personally, I'm not terribly concerned with a db becoming corrupt. If the server itself became non-functional, it wouldn't really matter.
... View more
01-19-2016
08:32 AM
|
1
|
0
|
5024
|
|
POST
|
Our production enterprise system is currently 1 sde gdb (Sql Server 2014) with several (45 to be exact) datasets and 9 editable versions (based on department). The sheer number of datasets makes it a little cumbersome for users to find what they may be searching for. I was wondering if anyone has tried breaking down a large sde gdb into several smaller gdbs, perhaps 1 sde gdb per department? If so, is there is a performance advantage of having 1 large sde gdb versus several smaller sde gdbs? Is response time better for smaller gdb versus larger gdbs? Would reducing the number of versions have a benefit on performance? I'm hoping to get some pros / cons of having 1 large sde gdb which is like a one-stop-shop for any GIS needs or several smaller sde gdbs meant for departmental needs. Thanks!
... View more
01-19-2016
08:21 AM
|
5
|
62
|
64251
|
|
POST
|
I'm wondering if anyone else out there has experienced a similar issue with 10.3.1 or if someone from Esri can duplicate my problem... I recently received a new machine and installed 10.3.1 on it and I seem to have an issue with feature classes not having the same SRID as the dataset they are contained within. If I create a similar dataset with 10.3 and do the same steps, I don't have this problem. Below are some details of the issue: 1) Dataset Working103 = dataset created with ArcGIS 10.3. SRID = 103045 (NAD 83 Iowa State Plane North 2011) 2) Dataset Working1031 = dataset created with ArcGIS 10.3.1. SRID = 103045 (NAD 83 Iowa State Plane North 2011) Next, I created a simple point feature class within each dataset, and inserted 3 features within each feature class. The feature class within the dataset created with 10.3 has the same SRID as the dataset, 103045. The feature class within the dataset created with 10.3.1 has a SRID of 6463, which I can't seem to find browsing through Esri's list of coordinate systems, so I have no idea what it is. Feature class within dataset created with 10.3 has the correct SRID Feature class within dataset created with 10.3.1 doesn't have the same SRID as the dataset If I do a spatial intersect query within Sql Server on the 2 feature classes using a polygon feature class from our production gdb, where all feature classes have a SRID of 103045, the feature class with the correct SRID returns results, while the other does not. Spatial intersect query works with dataset created in 10.3 bc SRIDs match Spatial intersect query does NOT work with dataset created in 10.3.1 bc SRIDs do NOT match Has anyone else experienced this issue...? Is this a known bug...? Is this specific to our use of SRID 103045...?
... View more
12-21-2015
08:45 AM
|
0
|
1
|
3781
|
|
POST
|
After poking around, this generates something pretty similar to the locks table...
... View more
12-08-2015
02:51 PM
|
0
|
1
|
1010
|
|
POST
|
I'm wondering if it's possible to create a query within Sql Server that lists the users that have a lock on a feature class...?...something similar to what you'd see within the 'Locks' view of the Gdb Administration. I'm assuming this is stored within various 'sde_' tables and related through identifiers. I'm hoping someone from Esri could point me in the right direction. We aren't looking to alter any of the background 'sde_' tables, just looking to reproduce the query that generates such a list. Thanks!
... View more
12-08-2015
02:23 PM
|
0
|
2
|
3716
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 02-03-2026 09:59 AM | |
| 1 | 03-02-2026 11:02 AM | |
| 6 | 02-18-2026 04:58 PM | |
| 2 | 02-18-2026 05:01 PM | |
| 1 | 12-09-2025 07:06 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 weeks ago
|