With almost any Portal there comes a time when you have dozens of items, created over time by different people, and you may be looking to perform a bit of a clean-up.
The problem now arises that you do not know if the Web Map made by a colleague, who since left the organisation, can be deleted or if it is being used by any other items? You might find that deleting an insignificant-looking item brings your organisation’s most-used application down.
Whenever a user runs into some sort of problem with the GIS system, one of the first things to look at would be the relevant logs. These give a more detailed insight into what is happening and where potential problems were encountered. This post will explain exactly how to obtain every type of log in the ArcGIS Enterprise stack.
So, you’ve got your new database set up by IT or your vendor, you create an Enterprise Geodatabase on top of it and you’re good to go! Not quite. There is a tendency for a gap to form between the maintenance tasks required for a RDBMS and a Geodatabase. Normally, the IT department will not be aware of the specific requirements of an Enterprise Geodatabase. Below are some key points to consider: