February 15, 2019 at 9:56 am
Video demo here:
Hi all, I’ve been working on the logic for this program for a few weekends now and was wondering what kind of features would make sense to add in an application meant to dissect and analyze large flat files.
I routinely recieve flat files in the 2gb+ range, and sometimes scraping a schema out of a 200 column extract (even with guidance) can be a pain in the ass. I created this tool to analyze those files and if wanted, inject a new connection manager into SSIS packages with a schema that matches the corresponding “create table” sql that it currently creates.
I’m already planning on adding warnings for things like nonqualified extra delimiters in lines, nonqualified quotes etc, but want to see if there are any opinions on what to add!
This will be open source when I push a beta version to github.
February 15, 2019 at 10:43 am
not to let down the work you have done but have you considered using a tool like http://record-editor.sourceforge.net/ which has most likely a significant part of the functionality you are after?
At least it may give you some ideas for what you are doing.
February 15, 2019 at 10:58 am
frederico_fonseca - Friday, February 15, 2019 10:43 AMnot to let down the work you have done but have you considered using a tool like http://record-editor.sourceforge.net/ which has most likely a significant part of the functionality you are after?
At least it may give you some ideas for what you are doing.
Thanks for the link! It looks like that tool is for viewing and editing flat files. Unfortunately what I need is something that quickly generates SSIS flat file connection managers fitting each column into useable data types. These are always large files I've never touched before. I need to parse through a very large subset of the data and check that they conform to these data types, and have no issues that will inadvertently blow up an SSIS import.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply