To support the implementation of new reports, Active Directory data will be downloaded to a
SQL Server database by using a SQL Server Integration Services (SSIS) 2012 package.
The following requirements must be met:
All the user information for a given Active Directory group must be downloaded to a SQL
Server table. The download process must traverse the Active Directory hierarchy recursively.
You need to configure the package to meet the requirements by using the least development
effort.
What should you use?
A.
script component
B.
custom component
C.
XML source
D.
script task
reckon the answer should be d.) script task
0
0
why a task?
0
0
In Control Flow I reccon you have to loop through the Active Directory with a Script Task and create a Data Flow Task to get the data. In the Data Flow Task you would create a Script Component.
0
0
After reading the AD-information by Script Task (agree with Roel) you choose the Task Execute SQL to writing the data in database. Or you use the same ScriptTask to writing in database. It’s possible too.
I think a Data Flow Task (into a Script Component) isn’t necessary.
0
0
Definitely A
http://sqljunkieshare.com/2013/05/22/importing-entire-active-directory-information-using-ssis-and-net-framework-3-5-and-above/
0
0
See Question 170 – it’s the same
0
0
You got it!
0
0
My question: Can the Script Component solution “traverse the Active Directory hierarchy recursively?” I tried Yuriy’s suggested post in my lab, altering and changing parameters to suit my environment, but only got it to work with SQL Server 2008 R2. Even at that, it kept returning the same data-set with every execution of the package. Not much luck with 2012. Anyway, I guess I’d stick with the Script component answer.
0
0