Enterprise Database - Unmet Needs

[atdservicebot]

This issue compiles features and capabilities that DTS Geospatial would like to see in an ideal enterprise database:

• Ability to manage locks on ATD-owned data
• Ability to work without having edits performed on MAINT by other departments slow down performance
• Ability to work in versions that are then reconciled and posted to DEFAULT
• Ability to have working versions longer then one week for long term projects as CTM currently deletes all versions every Friday

@jaime-mckeown feel free to edit the above and add your own thoughts and feelings about our current enterprise database onto this issue; I added a couple just to get started. After speaking with John this afternoon, this seemed like the best way to move towards a better enterprise database.

Migrated from atd-geospatial #237

[atdservicebot]

From alan-deanda on 2019-09-23:

Errors about datasets not currently being edited like this one can occur at random frequency:

[alan-deanda]

@andrewshensky we use this epic to track issues with our enterprise databases (MAINT, DM, etc) in order to build a case for creating our own databases in the server.

[jaime-mckeown]

adding @andrewshensky to this Epic.