Showing posts with label editor. Show all posts
Showing posts with label editor. Show all posts

Tuesday, March 27, 2012

ForEach Loop Editor

Help,

Trying to through a process together and using the "ForEach Loop" task. When configuring the task and using the ForEach Loop Editor I do not have the "ForEach File Enumerator" in the drop down. Anyone know whats going on or what I need to do to make this appear. I only see 5 selections: ADO, ADO.Net Schema Rowset, Variable, NodeList, and SMO Enumerators. I am also using the SQL 2005 eval with SP1.

Thanks,

John

This has been asked many times before:

https://forums.microsoft.com/MSDN/Search/Search.aspx?words=enumerator+missing&localechoice=9&SiteID=1&searchscope=forumscope&ForumID=80

-Jamie

|||

Jamie,

Thanks for the info, but feel uncomfortable since I have never compiled C# and not sure if I can do this within BIDS. After reading the posts it appears that some of the registry settings do not have the correct permissions. Would you happen to know which reg settings I need change the permissions for and what permissions they need to have?

Thanks,

John

Monday, March 26, 2012

ForEach file in folder - missing from dropdown list

I'm working through the SSIS tutorial, and am on lesson 2.
This says
"Double-click Foreach File in Folder to reopen the Foreach Loop Editor.

Click Collection.

On the Collection page, select Foreach File Enumerator."

The drop down only contains

foreach ado enumerator
foreach ado.net schema_rowset.enumerator
foreach from variable.enumerator
foreach nodelist.enumerator
foreach smo.enumerator

How do I get the "foreach file in folder" to appear in the drop down list?

Gary
A quick search of the forum will yield you the answer to your question.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1461435&SiteID=1|||

Mmmn,

I got our technical support team to load the sql server service pack 2 to fix another problem a couple of days ago.

This has not cured this problem (but did fix the other problem I was having).

Funny enough, both problems indicated that certain registry keys could not be read..

I'll get our technical support team to set up a restricted user and run the C# program the knowledgebase article gives.

Gary