Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Pull profiles from database

  Asked By: Jay    Date: Oct 05    Category: MOSS    Views: 1002

We're looking to import our profiles from a SQL Server database. We're
running Standard licensing. (Would we have to go to Enterprise licensing
for ALL CALS to pull profile data? Probably...)

Has anyone tried the 'SharePoint 2007 Shared Services Provider User
Profile Importer' available at
http://www.codeplex.com/MOSSProfileImport?

Share: 

 

11 Answers Found

 
Answer #1    Answered By: Deven Gajjar     Answered On: Oct 05

You say that your source is a SQL server database  correct? What should it
matter whether it be Standard Edition or Enterprise Edition? Furthermore,
the concept of profiles, do you understand what you're talking about?
Typically profiles  are the information that surrounds a user (LDAP / AD /
etc.). Are you looking to have your user profiles based off of a SQL
database table?

 
Answer #2    Answered By: Latisha Schneider     Answered On: Oct 05

Yes, our source is a SQL Server database.

What I meant to say was that we understand that we can import  profiles
from a database  source using the BDC. (I totally left out all reference
to the BDC in my previous message!) However, Enterprise licensing  is
required to use the BDC. Would we need to purchase Enterprise CALS for
every user with a profile  if we used the BDC to import profiles?
Assuming that's the case, we'd like to investigate a profile import
method that does not require the BDC (since we have no other use for the
BDC).

I believe that I do have a partial understanding of user profiles. They
are the source of user-specific information in places such as MySites,
and for People Search. They are not used for authentication or
authorization, except for cases where permissions are granted to
specific users or to sharepoint  groups containing specific users. All of
our permissions are granted to Active Directory security groups.

Yes, we are looking at having our user profiles  based off of a SQL
database table (a view, actually). The reason for this is that our
Active Directory is incomplete. We have users that we want to appear in
People Search that do not have entries in Active Directory. We also have
data in the database that does not appear in Active Directory
(photographs).

 
Answer #3    Answered By: Nora Maxwell     Answered On: Oct 05

The CAL level you purchase is based on the license level of the server. If
the server  is Enterprise then the CALs all need to be Enterprise. As I
understand it you don't get to buy lower level CALs because a user won't be
using Enterprise features.



The tool that you mentioned could be used to do a profile import  from a
properly formatted XML file. The limitation is that it is designed more to
be a tool for migration of information, not a recurring update. So I doubt
there is logic built in for what to do when the profile  info in SharePoint
has been updated by the user and doesn't match what is being imported. You
would also have to find a way to re-run the tool on a scheduled basis. I
don't think you would be able to use the normal Profile Import scheduler.
You will also need some field in the SQL database  being imported that
matches one of the Index fields in a normal Profile that ties the Profile to
a particular user.

 
Answer #4    Answered By: Faith Delgado     Answered On: Oct 05

Which are the Index fields in a normal profile? "Account" looks like one
- are there others?

 
Answer #5    Answered By: Irving Hurley     Answered On: Oct 05

SID??????????????????????????????????????????

 
Answer #6    Answered By: Trevor Davis     Answered On: Oct 05

Security ID....................

 
Answer #7    Answered By: Vinay Thakur     Answered On: Oct 05

my question wasn't stated very well!

Is SID an index field in a normal profile?

 
Answer #8    Answered By: Shayla Mcbride     Answered On: Oct 05

Security ID is the number that the operating system uses to distinguish
between one user account and another. If you delete a user and recreate
them you will get a different SID in active directory and they will not be
the same user as far as active directory is concerned. SIDs are used to
secure resource in the operating system. So for example it is the SID that
is actually used to record the NTFS (NTFileSystem) rights that a person has
to a file on a disk drive.

 
Answer #9    Answered By: Jarvis Rowe     Answered On: Oct 05

However, it looks like I asked the wrong
question again!!

You had said:

"You will also need some field in the SQL database  being imported that
matches one of the Index fields in a normal profile  that ties the
Profile to a particular user."

My question is about matching the users in the SQL database to the user
profiles. Is the AD SID used to do this matching? Is the AD SID a
profile index field in SharePoint?

 
Answer #10    Answered By: Selena Glenn     Answered On: Oct 05

Nope, you wouldn't use the SID to match. I would assume you would use the
AD userPrincipalName (email address format) or SAMaccountName (traditional
NT UserID) . Both of these are index fields in Profiles.

 
Answer #11    Answered By: Christian Waters     Answered On: Oct 05

MOSS uses distinguishedname by default for the username attribute (at
least with SSP user Profiles)

 
Didn't find what you were looking for? Find more on Pull profiles from database Or get search suggestion and latest updates.




Tagged: