Thank you for that info. I am new to gdb management so I am not sure if I will answer these correctly.
1. "Registering as Versioned"-Don't know what this means. I don't have SDE installed.
2. Don't have SDE installed.
3. I think this is what I am looking for.
To clarify, I have created a gdb in ArcMap 10.2.2 Catalog with 214,000 features. Since at this time, anyone can edit (and potentially delete data) the gdb, this is a problem that we are trying to address. I have been looking for the best way to accomplish this task. From what I gather, we need to create roles that have admin/edit/read-only capabilities to be able to keep track of when/who made changes and to allow us to have a rollback feature for "accidents".
It is my understanding that this is where versioning the gdb comes into play. I could be wrong, but from what I read was that I need a database management system, ex SQL, postgress, etc to be able to maintain multiple versions as changes are made to the gdb. I chose SQL based off of ease of use recommendations. I have installed 2014 SQL Express (which is free, but not supported as you stated in the previous post which I will change). I have not been able to figure out what to do next which is why I am here. I am looking for a workflow to explain what I need (as stated in the begining) to accomplish what we are trying to do. I hope this helps.
We have ArcMap 10.1 and 10.2 on numerous machines in our office with a single IIS Server machine. That Server hosts ArcServer 10.2.1 and SQL (don't know if that is best practice). My machine/role is admin for the server and gdms.
