ssisdfs Discussions Rss Feed

New Post: Expression Support

renegrin — Sat, 16 Mar 2013 23:21:01 GMT

Is it possible to add support for property expressions to the component? This would allow you add an expression to any read/write property on the component. This would be greatly helpful for reuse.

New Post: Looks like, SQL Server 2012 solved all these issues

tempdb — Wed, 04 Jul 2012 04:51:32 GMT

I tried SQL Server 2012 flat file connector. It seems it solved most of the issues that were present in SQL Server 2008 R2- Flat file connector. So, if you can upgrade to SQL Server 2012, you do not need this DFS component.

New Post: SQL Agent

dARYl — Mon, 11 Jun 2012 19:38:46 GMT

Hello.

I try to schedule SSIS package using DF2008 in SQL Agent but i have problems. When i am logged into server the job finish with success. When i am logged out it fails. I tried using proxies accounts but the same problem as someone described here: http://www.sqlservercentral.com/Forums/Topic960262-391-1.aspx

I can start for example SQL Agent on user account then run Job with DFS2008 on it and it will work. It isn't good idea. I can't do like that.

Conclusion:

If user4 on LAP4 has started any process (for example SQL Agent started on user4 or Reporting Services) the job with DFS2008 will be succeed.

If user4 on LAP4 hasn't got started any process the job will fail.

How can i resolve that problem? Any idea?

Information from SQL Agent:

Executed as user: LAP2\user4. Microsoft (R) SQL Server Execute Package Utility Version 10.50.2500.0 for 32-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 20:39:45 Error: 2012-06-11 20:39:46.55 Code: 0xC004706B Source: DFS 2008 File Task SSIS.Pipeline Description: "component "DFS 2008" (1)" failed validation and returned validation status "VS_ISCORRUPT". End Error Error: 2012-06-11 20:39:46.55 Code: 0xC004700C Source: DFS 2008 File Task SSIS.Pipeline Description: One or more component failed validation. End Error Error: 2012-06-11 20:39:46.56 Code: 0xC0024107 Source: DFS 2008 File Task Description: There were errors during task validation. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 20:39:45 Finished: 20:39:46 Elapsed: 1.264 seconds. The package execution failed. The step failed.

New Post: The component doesn't show up on my Toolbox

sbright — Thu, 05 Apr 2012 02:17:33 GMT

I installed several times. I re-open my VS, but couldn't see the components in my Toolbox. I re-started Integration Service. But still I can't see the component on my Toolbox

New Post: Does not work, no documentation

SteveP123 — Mon, 27 Feb 2012 15:29:30 GMT

Where is the documentation on how to use this? It installs but that's it. Not even a readme file?

New Post: DT_Text fields and saving changes

dcthedba — Thu, 03 Nov 2011 18:31:16 GMT

Hi,

I realy appreciate the time you have spent getting a flat file source component that parses the text file better than the default.

But -- I have a problem with it. I cannot get it to take a DT_Text data type. It will take a DT_NTEXT -- but I don't want that.

And maybe the biggest thing I have is that I can't change all the "Advance" details on all columns at once. If I save one change at a time it keeps them. Except the DT_TEXT. It just goes back to DT_STR.

One other thing -- I tried removing the column with the delete column button. It did delete it. But to add a column back in (thinking if I created new column I could designate Text) It only puts new columns at bottom and there is no "reorder" ability.

New Post: CRLF not being read

CArthur — Tue, 25 Jan 2011 19:42:20 GMT

I have installed the Delimited File Source and created a very simple .txt file with 3 columns ending with a CRLF. The values are comma separated and enclosed in double quotes. I have the "Text qualifier" as ". The "Header row delimiter as {CR}{LF}. I've checked the "Column names in the first data row" and the "Treat empty strings as null" boxes. The "Row delimiter" is {CR}{LF} and the "Column delimiter" is Comma {,} (in the columns dialog box).

This is what my data file looks like:

mycolumn1,mycolumn2,mycolumn3
"c1","c2","c3"
"c11","c22","c33"

When I click on columns I see:

mycolumn1 mycolumn2 mycolumn3"c1" c2 c3"c11" c22 c33

It appears that the CRLF is not being read.

Anyone know what I need to do?

New Post: DFS 2008 with Sort on huge file fails

tempdb — Thu, 23 Dec 2010 19:41:29 GMT

Hi,

I am using DFS 2008 as a Data Flow Source within SSIS (2008 data center edition). My data flow is simple Flat file to Flat file transformation with a "Sort" step in between.

For a smaller sized file (e.g. 1000 rows), it works fine. But, when I use file with 96,000 rows, it fails just after/during sort. (It seems, the process hungs).

Does anybody have this problem before?

New Post: Data Underflow in Unstructured CSV

sbauer09 — Mon, 13 Dec 2010 00:41:53 GMT

Hello

Firstly, I am very new at SSIS so please excuse me if this is a silly question.

I have an issue reading an unstructured CSV. Below is an example of the data:

"00001","236563","TEXT","TEXT",12323.00,"TEXT"
"00002","356603","TEXT"
"00003","356603","TEXT"
"00004","236563","TEXT","TEXT",12323.00,"TEXT"

When I add a text file containing this data as the DFS source, previews all look promising... the data in the grid looks how I would expect it. However when I pass it on, lines 2 and 3 error with the following message:

2,70033,2010-12-13 11:35:44.059000000,Column 4,DT_STR,255,Truncation (underflow) - the number of columns provided was less than expected.,

Is there any way I can pass through these rows?

Thankyou

Shaun

New Post: creating Delimited File Source from program

YaakovN — Mon, 22 Nov 2010 17:57:03 GMT

For our system we create SSIS packages via a C# program from metadata.

We would like to use DFS2008 in our data flows. But I am struggling to figure out how to set the ArrayOfConfiguredFileColumn-property. I strongly suspect I need to use the "InsertStandardOutputColumn" procedure in "ComponentModel", which expects a "ConfiguredFileColumn" as parameter. But I cannot find the object from my DataFlow from which to call this function.

Could some wizard here provide an example please?

Thank you very much in advance, your help is much appreciated.

New Post: Data type conversion failure does not fail the DFS component

kharverson — Wed, 18 Aug 2010 15:47:25 GMT

I am having a similar problem. I have a column that is too long and is therefore getting truncated. Even though I've set everything I can find to "Fail Component", the component just ignores the error, ignores the row, and succeeds. I also found that if you redirect failed rows, it only works if you tick "Include error output audit columns" - otherwise it continues to just ignore the row.

New Post: DFS 2005 / VISTA Columns not loading after I select a File

kharverson — Wed, 18 Aug 2010 15:44:24 GMT

I just added the columns manually and they then work fine.

New Post: DFS 2005 / VISTA Columns not loading after I select a File

xun — Thu, 15 Jul 2010 13:06:55 GMT

i have exactly the same problem and have been struggling hard ...

New Post: DFS 2005 / VISTA Columns not loading after I select a File

crabsodyinblue — Thu, 15 Jul 2010 11:03:08 GMT

DFS 2005 - Columns not loading.

Manged to install the component but after I connect to the flat file , no columns appear in the editor.

Component appears in the toolbox, can drag and drop it... but can't get the columns of the delimeted file to appear in the DFS Editor

Running Visual Studio 2005 Version 8.0.50727.867

Operating System Vista Ultimate

New Post: The component could not be added to Dat Flow task

xun — Thu, 15 Jul 2010 07:30:44 GMT

i restarted ssis service. it worked. At least it seemed. Then I found it did not pull any columns

New Post: Buffer error while parsing

dfoard — Wed, 23 Jun 2010 17:49:37 GMT

I am getting the following error while trying to read a tab delimited file: Size of the parsed data exceeded maximum parsing buffer size (65536).

Has anyone encountered this and if so is there a setting or a work around?

Dave

New Post: File Name Column property?

SvenAelterman — Fri, 14 May 2010 01:05:42 GMT

This is a very useful component for some of the troublesome files I encounter. There is one feature I am missing though: a File Name Column property, as is present in the SSIS Flat File Source. I wouldn't mind implementing it if I had an idea on how to get started.

New Post: Data type conversion failure does not fail the DFS component

gabbydy — Wed, 17 Feb 2010 03:44:24 GMT

I really like your tool and it solves my issues with missing columns. But it does not seem to handle data type conversions as errors. I have a column that has a data type of DT_DBDATE. I have set this colum to "Fail Component" on Error. When I pass the wrong value of "2010)02-15" (this is basically an error in the source file that we cannot seem to trace the root cause), the DFS component does not fail. It will identify the error when I output it using the Auditing options. But I thought that since I set it to Fail Component, the entire pipeline should stop with an error.

Thanks.

New Post: \" escape character

jasonus — Wed, 10 Feb 2010 14:06:19 GMT

Rob,

Just wondering if you ever got around to modifying the component?

Thanks much,

Jason

On Mon, Jan 18, 2010 at 5:20 PM, roblad <notifications@codeplex.com> wrote:

From: roblad

This is indeed an issue!

Quite a big one in fact, in that although I ask for an escape character on the UI I don't actually use it anywhere in the component!

I'll look to add and test this functionality over the next few days. I'll let you know when it's done.

Regards,
Rob

Read the full discussion online.

To add a post to this discussion, reply to this email (ssisdfs@discussions.codeplex.com)

To start a new discussion for this project, email ssisdfs@discussions.codeplex.com

You are receiving this email because you subscribed to this discussion on CodePlex. You can unsubscribe on CodePlex.com.

Please note: Images and attachments will be removed from emails. Any posts to this discussion will also be available online at CodePlex.com

--
Jason Us
jasonus@gmail.com
802-771-7535

New Post: Installation on Windows Server 2003 x64

kartikr — Mon, 08 Feb 2010 05:52:35 GMT

Hello,

First of all, thanks for developing this component.

I wonder if I can get your advice on getting this to work in my environment.

I've tried two approaches to get this running on a Windows Server 2003 x64 machine running BIDS 2008.

1.) Ran the recommended installer, install was successful but the component does not show up in the Toolbox under SSIS Data Flow Items.

If I open an existing SSIS 2008 package that uses DFS2008 then there is a red cross over the component, the icon switches to XML source and I get an object reference error when I try to view the properties.

2.) Tried the alternate installation method which was to download the DLL, I placed this in the PipelineComponents folder.

I was able to get component to show up in the toolbox, however when I run a test package I get the below error, thought it might be because the DLL is not registered however if I try to register the DLL with regsvr32 then I get a entry point cannot be found error.

Bottom-line is I cannot get things to work in this environment.

Is DFS 2008 incompatible with my current environment or am I doing something completely daft ?

Cheers.

TRACE FROM APPROACH 2

Error: 0xC00490F7 at Data Flow Task, Data Flow Task (CSV [1]): The managed pipeline component "DatabaseGroup.SSIS.SourceAdapters.DelimitedFileSource2008Component, DatabaseGroup.SSIS.SourceAdapters.DelimitedFileSource2008, Version=1.0.7.0, Culture=neutral, PublicKeyToken=103567041829a1c2" could not be loaded. The exception was: Could not load file or assembly 'DatabaseGroup.SSIS.SourceAdapters.DelimitedFileSource2008, Version=1.0.7.0, Culture=neutral, PublicKeyToken=103567041829a1c2' or one of its dependencies. The system cannot find the file specified..

Error: 0xC0047067 at Data Flow Task, Data Flow Task (SSIS.Pipeline): The "component "CSV" (1)" failed to cache the component metadata object and returned error code 0x80131600.

Error: 0xC004706C at Data Flow Task, Data Flow Task (SSIS.Pipeline): Component "component "CSV" (1)" could not be created and returned error code 0xC0047067. Make sure that the component is registered correctly.

Error: 0xC0048021 at Data Flow Task, Data Flow Task (CSV [1]): The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "www.databasegroup.co.uk".

Error: 0xC004801F at Data Flow Task, Data Flow Task (SSIS.Pipeline): The component metadata for "component "CSV" (1)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

SSIS package "Package.dtsx" starting.

Error: 0xC004801F at Data Flow Task, SSIS.Pipeline: The component metadata for "component "CSV" (1)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.

Error: 0xC0048021 at Data Flow Task, CSV [1]: The component is missing, not registered, not upgradeable, or missing required interfaces. The contact information for this component is "www.databasegroup.co.uk".

Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "CSV" (1) failed validation and returned error code 0xC0048021.

Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.

Error: 0xC0047067 at Data Flow Task, Data Flow Task (SSIS.Pipeline): The "component "CSV" (1)" failed to cache the component metadata object and returned error code 0x80131600.

SSIS package "Package.dtsx" starting.

Error: 0xC004801F at Data Flow Task, SSIS.Pipeline: The component metadata for "component "CSV" (1)" could not be upgraded to the newer version of the component. The PerformUpgrade method failed.

Information: 0x4004300A at Data Flow Task, SSIS.Pipeline: Validation phase is beginning.

Error: 0xC0047017 at Data Flow Task, SSIS.Pipeline: component "CSV" (1) failed validation and returned error code 0xC0048021.

Error: 0xC004700C at Data Flow Task, SSIS.Pipeline: One or more component failed validation.