In a SQL database there could be many Tables and Views that are not participating in the Enterprise Geodatabase. The current Create Layers process on a Data Store creates layers for EVERY Table and View, which makes the Content list extremely cluttered. A better option would be to:
- Allow users to select which Tables and/or Views to Publish.
- ONLY publish Tables that are participating in the Geodatabase