Latest Contributions by KevinDunlop

Check out X-ray for ArcCatalog (https://www.arcgis.com/home/item.html?id=9ea218ff575f4a5195e01a2cae03a0ae).  It allows you to export your database schema to HTML web page that lists all feature classes and their attributes.   ... View more

I had this happen to me once.  The issue was related to a relationship class we had.  One table had orphan records which the other did not have a counterpart for.  This caused the sync on the replica to spin and spin until it finally just timed out.  When I deleted the orphans, it starting working again without issue.  ESRI support wasn't much help here and I just had to do trial and error to until I found the issue.  I have heard this also can happen if you have a bad geometry value in one of the records. ... View more

When you load the mxd in ArcMap what type of database authentication are you using?  If you are using OS authentication, your personal account might have access to the data while the account ArcGIS server has stored for that database might not. ... View more

I am not sure I understand your problem.  Are you interested in finding all calendar dates that fall within 90 days of this time each year. Or are you trying to find all dates that are 90 days within a provided past date?  Those two problems would have different solutions. For the first question.  It is not perfect since it assumes each month has exactly 30 days.   ( EXTRACT ( MONTH FROM Start_Date ) - 1 ) * 30 +   EXTRACT ( DAY FROM Start_Date ) BETWEEN ( ( EXTRACT ( MONTH FROM CURRENT_DATE ) - 1 ) * 30 +   EXTRACT ( DAY FROM CURRENT_DATE ) - 90 ) AND ( ( EXTRACT ( MONTH FROM CURRENT_DATE ) - 1 ) * 30 +   EXTRACT ( DAY FROM CURRENT_DATE ) ) ‍‍‍‍‍‍ ‍ ‍ ‍ That means for today this would return values like 8/12/2016 9/15/2018 10/22/2003 You can easily substitute CURRENT DATE with any date (see below as example). As for the second one here it could be any date: Start_date >= date '2017-10-22' - 90 and start_date <= date '2017-10-22' ‍ This will return all dates between July 24, 2017 and Oct 22, 2017.   In both solutions, it assumes you are interested in only 90 days before the given date.  You can change this by adding 90 to second date listed. ... View more

I missed the part where you said it was FGDB. That would be: Start_Date >= CURRENT_DATE -90 If you don't use something like this and only the DD/MM then the years will be an issue.  The method you are trying would return records 2 and 3 when they are both pass 90 days ago. ... View more

This depends on your database.  For SQL Server the easiest way is  Start_Date >= getdate ( ) - 90 ‍ For PostgreSQL it is: Start_Date >= now ( ) - INTERVAL '90 DAY' ‍ ... View more

Will the feature service sync be a real time process where edits automatically sent to both databases or will it be a process that must be kicked off (like current replica sync)?  If it is real time then it could cause problems. For example if one of editors deleted all the records out of a synced feature class, then all our web users would be screaming at us.  By being able to control when a sync happens, we can roll back data if needed when something like this happens.  And it has happened before. Secondly, will the sync feature service affect performance on both databases and what happens if one is lagging?  We use replication to separate our desktop production users from our web traffic which is mostly read only.  We replicate the production database to an internal web database and an external web database.  This has saved us several times where one system would get hammered while the others were not.  We have had scripts kick off in production database that brought it to its knees but our web services were unaffected since their database was separate.  Like wise we have had massive spikes in our web traffic (10,000 times normal) when an external users pounds us. When that happened our production databases wasn't affected since it was separated.  Have a feature service that connects them risks them having impacts from each other.   ... View more

LUPAPWC was the name of the feature class I used for the example (it was the one I had open at the time I made the post).  The archive always pulls from the default version of the feature class so my script does the same.  There is currently no archives for user versions. The ArcCutDate is a table is used solely for this process.  I created so you can run multiple rebuilds at once (I recommend against this since this process can be a resource hog especially on very large feature classes).  That is why it stores the table name along with the min date.  Iit doesn't use any version and is not part of SDE. Hope that helps. ... View more