I have been implementing a FIM2010 server as part of a solution that will ultimately upgrade ILM server to FIM. We are importing data from AD and exporting to a database. One of my users has an attribute containing a 450 character string. This works fine in ILM becausse the default type in mms_metaverse seems to be nvarchar(450) but when I attempt to synchronise in FIM it causes an unexpected-error. Investigation showed that to be a SQL stack overflow and looking at the mms-metaverse table for FIM all the defaults that were nvarchar(450) in ILM now appear to be nvarchar(448). Is this right or am I missing something? If this is the case, is this difference between ILM and FIM documented somewhere? I ran a pretty extensive search and could not find anything. Cheers, Eddie

There isn't much in the world about the database construction in ILM or FIM. I would imagine that this is by design -- Microsoft doesn't support any modifications to the database, and, I am sure doesn't document as a result. I am quite sure that change isn't documented, but it does seem to be the case... I am curious about what is represented with a 450 character string in your MV :)Aaron Sankey, Avanade