Hello,
Can i delete records of Delta table (A & D) in SQL Enterprise Geodatabase using SQL?
Thanks.
- 3 people found this helpful
No. You should not play with the Tables in a Geodatabase from the database end. Inconsistencies may occur later.
Maybe you can share the issue, which is leading you to delete the records from the Delta tables and can find a solution for that here.
I used the Compress Geoprocessing Tool to compress a geodatabase but sde compress didn't empty delta table.
And I can't Full Compress because I can't delete version tree in enterprise geodatabase. It relate to my replication geodatabase, map services and feature services when I published.
- 3 people found this helpful
Partial Compress is not an issue.
You can do the Full Compress later sometime by deciding upon a convenient downtime for that geodatabase. take a look at this link:
Acheiving Full Compress on Geodatabases with Existing Replicas | Support Services Blog
I used Partial Compress but not work. This is version diagnose:
74309 rows referencing nonexistent states found in PHUWAGISV1.SDE.a73 (PHUWAGISV1.SDE.FCDONGHOKHACHHANG)
74309 rows referencing nonexistent states found in PHUWAGISV1.SDE.d73 (PHUWAGISV1.SDE.FCDONGHOKHACHHANG)
Diagnose Tables: 99 multiversioned tables examined,
1 multiversioned tables had orphaned, duplicate, missing or redundant rows.Can you help me next steps?
I believe that you shared the results from the Diagnose tools. You can take a full DB backup and then execute the Repair tool. Repair Version Tables—Help | ArcGIS Desktop
However, I'll recommend that if you are not completely sure, contact Esri Tech Support and they can guide you on a call and a quick screen sharing session.
Thanks Asrujit SenGupta.
I'll try.
- 1 person found this helpful
I have solved this problem.
I used Repair Version Tables tool.
Thanks.
Great! Close the thread if your question has been answered by marking the appropriate response as "Mark Correct"
- 2 people found this helpful
This is called a Partial Compress and can be expected in multiple scenarios:
1. There are editors editing when you ran the compress
2. Because of Orphaned connections
3. ArcGIS Server services are running
Geodatabase compression—Help | ArcGIS Desktop
In a fully compressed geodatabase, there are no rows in the delta tables and the state tree is trimmed back to zero. Performance improvement is greatest if the geodatabase is fully compressed. To achieve this, do the following:
- Reconcile and post all outstanding changes in child versions to the DEFAULT version. As the geodatabase administrator, you can see in what order versions should be reconciled by default by opening the Reconcile Order subtab of the Versions tab on the Geodatabase Administration dialog box. See Version properties for information on the Reconcile Order subtab.
- Delete the versions themselves after you have reconciled and posted edits.
- Make sure no user is connected.
- Perform the compression operation.
So try these steps and then let us know if there are still records left in the Delta Tables after the Compress operation.
I believe that you shared the results from the Diagnose tools. You can take a full DB backup and then execute the Repair tool. Repair Version Tables—Help | ArcGIS Desktop
However, I'll recommend that if you are not completely sure, contact Esri Tech Support and they can guide you on a call and a quick screen sharing session.