September 6, 2007 at 7:57 am
You're ignoring bad rows?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2007 at 7:58 am
The Max Error Count on the parent objects is what I was missing also. My package is now running
John M., can you explain further about the Event Handler Propagate Variable? Where is this located?
September 6, 2007 at 5:48 pm
Jeff, in my situation I could ignore the bad rows and just segregate the bad files into another folder. Our urgent need is to process many files, from which we do not have a very large possibility for bad files. In the long term, I'm sure we'll want to add some smarts into the OnError event handler to work with the bad stuff.
Janice, the easieast way that I've found to work with the appropriate variables is to navigate down to them through the Package Explorer tab. After you've created an event handler on your data flow task, you'll be able to expand the Event Handler and OnError folders. The System :: Propagate variable is in that Variables folder.
This stuff is very new to me also, I found this Propagate variable method through much searching through the SQL Server 2005 Books Online. I'd be very curious to know if this is the best approach, but it seems to be meeting my needs for now.
September 7, 2007 at 2:00 pm
Thanks John. It's amazing what you can find when you know where to look. I didn't know all those variables were available
September 12, 2007 at 5:28 pm
Hi All,
I am afraid I am back with another puzzle. I have a package with a ForEach Loop container which loops thru a set of files (.mdb) in a folder to and imports them to SQL server. I have mapped the Directory property of the container to a variable and have created a package configuration file so that I can modify the location of the folder without having to recompile the package.
The problem I am facing is using a UNC path to point to the folder. I need to use a UNC path as the folder resides on a different box (webserver) from the database server. If I use the full non-UNC path (i.e. d:\inetpub\wwwroot\...) everything works perfectly. If I use the UNC share name the package does not find the files and returns the following warning.
Warning: The For Each File enumerator is empty. The For Each File enumerator did not find any files that matched the file pattern, or the specified directory was empty.
Does SSIS not support UNC paths for the Directory property or am I doing something wrong?
Thanks again for your help
Calvin
September 12, 2007 at 5:41 pm
As an additional side note, I am still in development so the DB and Web server are on the same box. I just shared the folder on the local machine and trying to access it from SSIS as \\localhost\brmf_uploads
So everything is local at the moment.
September 13, 2007 at 5:11 am
I would remove the possibility of the unc path being an issue by using a local folder on the server. This will make sure your tasks and packages work properly. Then try adding the unc pathing. At this point you could pop the variable paths to the screen with a msgbox if you are setting variables up in a scipt task. Then you know if you've built the path properly.
September 13, 2007 at 9:32 pm
The problem with the UNC is that the server must be logged in as a "super domain user" than can "see" those other boxes and directories...
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 8 posts - 16 through 22 (of 22 total)
You must be logged in to reply to this topic. Login to reply