I have recipient data in CSV formatted dump files and need to synchronise it into AD via FIM Synch - could somebody possibly outline the best way of doing this? Is it still achieved by using SSIS to import the data into tables, then generate views for the SQL MA? Into Synch engine then out to AD? TIA

Which functionality do you wish to achieve and what are your requirements? - How is the data provided? Full collection only, or do you have a delta file available too? - What kind of exports are needed (export only or full collection) - do you have a delta attribute which indicates the changes (add, update, delete, ...) - Do you need other FIM functionality except for FIM Sync? If you're sticking to FIM Sync only, you could handle the case just like you would with ILM 2007. In that case, it's all documented in the Getting started collection, check : - Synchronizing SQL Server Objects to Active Directory.doc - Generating Delta Views Using Triggers.doc - Generating Delta Views Using Snapshots.doc If you need help with SSIS : Flat File Imports with SQL Server Integration Services 2008. Or SSIS in SQL Books online... Kind regards, Peter Peter Geelen - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]

Hi Peter, many thanks for the response.. I have full collection only, no delta's. I was hoping to be able to synchronise these recipient objects using declarative provisioning within FIM - do you know if there is a 'how-to' guide available for this scenario? Also, does the FIM SQL MA support the update column as per MIIS/ILM? I guess if we are only working with full collections, we must stage the data in a table, compare the data with the previous table, and generate a differences table that indicates the changes? Does this sound possible? Do we know what the big gotcha's are with this scenario? For example, handling import errors? Checking that objects already exist, etc. Thanks again

I belief, you are talking about this: Generating Delta Views Using Snapshots Generating Delta Views Using Triggers Cheers, Markus Markus Vilcinskas, Knowledge Engineer, Microsoft Corporation

Regarding the big gotcha's, IMHO, it rather depends on your config and your data quality... Handling import errors and duplicate object checking is not specific to this scenario (SQL <> AD), but general management agent configuration. Carefully planning your configuration, and thoroughly testing will be the most important task to think of. HTH, PeterPeter Geelen - Sr. Consultant IDA (http://www.fim2010.be) [If a post helps to resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of that post. By marking a post as Answered or Helpful, you help others find the answer faster.]