Latest Contributions by KevinDunlop

sorry, try removing the AS keywords.  They are not used with table names in Oracle. ... View more

1.  You will only have the option to Register as Version if Archiving is turned on.  If not, then you will have both options.  You can't unregister even though the other features classes are already register as version since archiving was turn on.  I have attach a screen shot of what it looks like after you create a new feature class in a previously registered dataset with Archiving  and editor tracking turn on. 2.  See image and answer above.  Remember to register as versioned before enabling archiving. 3.  All field changes affect all versions.  Remove a field, and it removed from all versions.  Add a new field, and all versions have it with null value for that field.  No versions need to be delete to change the field.  User locks on the database will prevent you from making a field change. 4.  Yes H tables have the same schema as the normal table (plus the additional fields need for archiving to work). Hope that helps. ... View more

It sounds like it could be a few things. 1.  Wrong username/password 2. The database account is disable/locked.  It could also be that it is not granted permissions to connect to that SQL Server instance. 3. The database was created on one SQL Instance but was moved to another one.  User accounts need to be created instance level, then assigned to the database.  If moved the database to a different instance (like an always on failover or restoring a back up), the database level accounts might not be in the instance. 4. SQL Server Instance was changed to use only Windows Authentication mode. What your image shows is the account running the SQL Server software.  I would not change this if possible.   ... View more

I am doing this from memory so hopefully I get it all right.  The biggest problem is that you must clear locks prior to most of these changes (ie disconnect users). 1. Field addition/deletion/renaming or any other field change. -Does not require disabling stuff. 2. Domain creation/modification. -Does not require disabling stuff 3. New Feature class/Table creation. -Does not require disabling stuff. -If added inside a dataset, you will need to enable it again (old stuff remains unaffected) depending on your GDB version.  Otherwise, the new item won't have versioning/archiving set. 4. New relationship class creation. -Does not require disabling stuff -Changing item may requires disabling versioning and archiving -Adding topologies requires disabling versioning and archiving. 5. Enable Z-Aware or M-Aware on existing Feature Classes. -I don't think you can once it is created. 6. Unregister replica and create new replica. -Requires versioning to be enabled. 7. Add/modify subtype to existing Feature Class. -Does not require disabling stuff. 8. Assign or modify privileges on feature datasets. -Does not require disabling stuff. ... View more

For the large datasets, we encounter similar issues.  The problem lie in that shapefiles have a 4GB limit on size and is the default format for non-host services.  Our contours came in at around 9 GB so we had to break the layer up into smaller subset feature classes. ... View more

This is because ArcGIS uses the database syntax to handle where clauses.  Every database is slightly different with different functions.  Something that works in Oracle may not working SQL Server.  Something in a File GDB may not work in Postgres.  And so on.  The document you reference refers to this: Other databases Please consult the database's function documentation and syntax. For example, SQL server uses the same DATEPART function as personal geodatabases, but with slightly different syntax: So you need to look up the proper way to query a year for your database type.  Which database are you working with? ... View more

How are you running your code?  In ArcCatalog, command line, or a python IDE (like pyscripter)?  I believe Arcpy.Addmessage won't print to command line or in python IDE.  So try adding a line below it that uses the print command. ... View more

I used the default size personally and didn't have a problem. I found not go has high as 64K since if you need only 1 bit, then you must access the full 64k worth compare to only 4K or even 8K with smaller blocks. I know that you are using SQL Server but check out https://community.esri.com/thread/115952  Hope that helps. ... View more

It would be help to have more information.  Your post is rather vague. 1. Is the feature class or table you want to have a trigger on versioned?   2.  How are you flights inputted? Manual or automated.  What is the process? 3. What is the trigger code you are using? 4. Are you using workflow manager? 5. When would the valve condition trigger fire?  On flight input?  on inspection?  nightly/daily? ... View more