We've been making out editors run scripted Data Reviewer against their SDE versions prior to posting for over a year now, and have frustrated enough users that we are investigating a process to export the changed records in the version out to File GDB just to run Data Reviewer. Our test version summary:
100 edited records in TEST1_POLY (of 68125 total records)
100 edited records in TEST2_POLY (of 83631)
100 edited records in TEST3_POLY (of 54762)
There are about 15 checks in the RBJ for each feature class, most are SQL checks.
~ 30 minutes to run Data Reviewer against the user's version (changed records only)
~ 2 minutes to export the changed data to file GDB and run Data Reviewer against it... and more than half of the 2 min. was to do the export.
Needless to say, that's enough evidence that we're going to throw some more resources at this prototype. We do recognize that some checks will not work against the exported file GDB data (such as validating unique values across the entire feature class) and we might need to have two separate RBJ files - one run against the database, another against the exported file GDB data. There will need to be a step to link the file GDB results back to the SDE objectids for the final report, but I can't imagine that will be significant. There are other issues to sort out as well.
If anyone has attempted something similar or has a different idea on how to work-around the abysmally slow Data Reviewer in SDE processing, we'd love to hear about it...
-Steve