The following is to request assistance in explaining some of the IT Database resources in my city the reason why an enterprise geodatabase (in SQL) has many objects, tables, stored procedures that they consider are not needed. The issue came after geo-enabling a non-spatial database in the test environment in order to start incorporating GIS functionality into some of the web applications we currently support in-house. Since I am not a database administrator or developer by nature, I really cannot provide them the logical answers as of why after geo-enabling a database, all these objects are present in the database and why they are needed. They just want to start randomly deleting stuff they consider are ‘not needed’.
Thanks in advance!