Very early on in our FIM deployment, we ran into discussions regarding the need for schema changes in FIM.
The default schema is, in almost every case, not sufficient and needs to be modified.
I will only give a short overview in this chapter about this, and will try to explain more in the coming chapters, as we look into the details of FIM implementation at The Company.
One of the problems with the FIM Synchronization/FIM Service system is that it holds two schemas. We have one schema for the FIM Synchronization Service database and one for the FIM Service database.
Depending on our needs, we change one or both of these schemas. Whether the attributes or objects are required within FIM Service depends on whether or not they are managed using FIM Portal, or used in some policy. If not, we do not need them in the FIM Service schema.
On the other hand, if an attribute or object type is used in a policy within FIM Service, but is never supposed...