August 9, 2007 at 6:27 pm
Hi all,
I am trying to do some research for an upcoming project and was hoping someone here would have an idea on how to proceed. Is it better to store user profile data in AD, or in SQL Server. We have basic user data in AD already, so some people were suggesting that we put everything we need in there. Much of this data would be volatile.
The reason for all the extra information is to use the audience features of Sharepoint 2007 which we are currently rolling out. As far as I know, this version of sharepoint can take user profile data from a number of sources including SQL Server databases, which is why I am wondering where would the best place be for the data. Sharepoint is the only place we need this extra data.
Thanks for any help on this. I know very little about AD, so recommended reading is welcome.
TIA,
John
August 15, 2007 at 9:57 am
I would store all the user profile data in AD, where the user profiles are. If you wanted to store this data in SQL, you would have to then deal with the overhead of creating a similar data structure to handle this information , link to each user account, creation of a mechanism to ensure that you don't get orphan data, ensure that anyone who wants to change this data then has proper permissions to the database, etc. This can all be handled very simply (without having to create a new structure to store this information) within AD, plus you could also push this responsibility off to your network team, unless of course that's you. At any rate, with the additional overhead and maintenance that it would take to put in SQL for no apparent payoff I would suggest putting all of this information in AD.
John
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply