There are lots of duplicate views (vcollection, Vcollections) that stores almost the same information. To review and remove those duplicates would ease the use of the database.

Use unique identifiers - in rare cases the resourceid is called itemkey. Or the product code shows up sometimes as Software Code. A unified naming convention would be very appreciated.

Devide information for CI deployments/compliancy, those for applications, Security Upates, Deployment Types and whatnots. Having all stored to one table/view CI_ConfigurationItems is very confusing and very difficult to retrieve.

Outdated versions/revisions (apps, CIs) not in use should be removed also on the CAS by the maintenance tasks.

application data is stored in a XML format only. This is very, very hard to retrieve and link to all other items like Deployment-Types and Deployments. - Information on applications should be stored in a table/view instead.