Hello ,
I'm looking for an efficient way to compare the versioned SDE with the original SDE. I'd like to perform this comparison before running the compression and before posting the jobs in the database.
I believe it would be time-consuming to read and compare all tables from both the versioned and original SDE. Is there a method that would allow me to read only the specific tables that have been edited in the versioned SDE?
Thanks in advance
FME 2021
In the SDE Reader you can specify the Version to read - https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/geodatabase/GEODATABASE_SDE_reader.htm
By original SDE i’m assuming youre meaning the default version. So you can have one reader reading from default, and another reading from the specific version.
In terms of finding what FCs have been edited in the version, you should be able to construct an SQL query to query the adds/deletes tables to pull that information out (I’d class that as an advanced approach).
There are a couple of similar discussions here:
https://community.esri.com/t5/data-management-questions/see-edits-made-in-a-specific-sde-version-before/m-p/289279#M16549
I'm not very familiar with SQL.could you help me in sql query ,if possible .
What SQL query should I use within a feature reader to retrieve obj_id from all tables a and d
After obtaining obj_id, I have to search all feature classes that also contain this same obj_id .
then I want to get the data from matching feature classes as output.
I'm not very familiar with SQL.could you help me in sql query ,if possible .
What SQL query should I use within a feature reader to retrieve obj_id from all tables a and d
After obtaining obj_id, I have to search all feature classes that also contain this same obj_id .
then I want to get the data from matching feature classes as output.
I’ll be honest, if you’re not confident to create that select statement then that approach is not suitable for you. There are potentially dozens of adds and deletes tables and you’ll need to find the layer ID to find the correct table to look at. Then there are the various states/lineages/versions to look through
Probably the better approach is to look at some of the approaches in the Esri Community