ADSI and SQL Server is exactly what we are doing. Which works great because we also have to join that data with an Oracle server and then insert it all into tables in SQL Server.
In general I don't even get the memberOf fields for the stuff I'm doing. > -----Original Message----- > From: Dawson, Michael [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 24, 2006 2:06 PM > To: CF-Community > Subject: RE: Why is coldfusion better. > > The main problem comes when you are dealing with multi-value attributes > such as "member" or "memberOf". When these exceed 1000, Active > Directory does some funky things. > > You then have to perform a few tests before you can actually return the > data. > > This is an AD thing but related to LDAP since AD limits multi-value > attribute results to 1000 values. > > This is where I would use ADSI and SQL Server to do the refreshes. > > However, if you can guarantee there are less than 1000 values in a > multi-value attribute, then CF is just fine. > > Mind you, I have not yet tried this with SQL 2k5 yet, so it may be > easier than CF. > > If you wanted to stay mostly-CF, then create a COM object that retrieves > the values from AD. > > Performance-wise, I never really saw that SQL/ADSI was any faster than > CF/LDAP. > > M!ke ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Message: http://www.houseoffusion.com/lists.cfm/link=i:5:194070 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/5 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:5 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.5 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
