FIM Service Database size data point
It is an exciting time as customers plan & start to roll out their FIM 2010 deployments. One of the initial questions asked is how much hardware do I need? The team is working on providing some more documentation to help answer these types of questions, but for now I will share with you a data point that may help.
In an earlier post I included the hardware we are using to test performance in our lab. In this post I would like to give you a data point around scale & size of a given db used on this hardware.
First is a breakdown of the top objects in one of our test databases. This should help give you a reference point for thinking about if your deployment is bigger or smaller than what this db represents. Size will additionally vary based on the configuration, number of attributes, etc that are specific to your deployment.
Expected Rules Entries
Note: The requests & workflow instance counts are higher than I would expect in a deployment as I have not pruned this database down for completed objects.
Data file size
FIMService SQL Data (mdf)
FIMService SQL Log (ldf)
Note: The log file of course will grow over time & need to maintained via regular transaction backups.