If you’ve read through the release notes for the Forefront Identity Manager (FIM) 2010 hotfix rollup package, which contains build 4.0.3576.2, released on March 23, 2011 you might have noticed this succinct, but highly interesting point under the “Resolved issues and features that are related to Synchronization Service” section:
The performance of the SQL MA is slow. After you install this package, indexing operations are improved, and the performance of the SQL MA is 25 percent faster.
Upon reading this I immediately assumed that we’d changed the underlying provider. My understanding is that we use OLEDB for all the database management agents. I was wondering if we’d moved the SQL MA to the .NET data provider, so I asked the question on an internal forum and got this response back from Andreas Kjellman, Program Manager FIM Synchronization Service.
In the latest hotfix there is a ~25% performance increase for the SQL MA without changing the provider. In the latest fix we changed handling of Unicode so SQL can use indexes and can avoid table scans.
I thought that this was interesting enough to warrant a post and, truthfully, it enables me to test posting to Word Press via Word 2010. J