Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 1234»»»

Dynamic ETL with SSIS Expand / Collapse
Author
Message
Posted Monday, October 18, 2010 10:20 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Tuesday, May 20, 2014 4:43 PM
Points: 11, Visits: 77
Comments posted to this topic are about the item Dynamic ETL with SSIS
Post #1006708
Posted Tuesday, October 19, 2010 3:34 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 12, 2010 12:19 PM
Points: 5, Visits: 17
I don't know why you'd want to go to such lengths to use SSIS, just use Pervasive (formerly Data Junction). It's a far superior way of getting data into SQL.
Post #1006811
Posted Tuesday, October 19, 2010 4:38 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Today @ 9:56 AM
Points: 337, Visits: 1,988
Martyn Hughes (10/19/2010)
I don't know why you'd want to go to such lengths to use SSIS, just use Pervasive (formerly Data Junction). It's a far superior way of getting data into SQL.


I agree with you to a point but there are more elegant ways of doing this in SSIS

Sarah, you mention that SSIS requires a flat file format to load the data properly in to SQL Server... so why not create the bulk load format file on the fly using a script? its fairly easy to parse the file and determine number of columns, data types etc. and then build the format file and the destination table based on that information.

Post #1006844
Posted Tuesday, October 19, 2010 7:38 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, July 24, 2014 2:21 PM
Points: 12, Visits: 67
Great work, if you have a spare time to do so. I think SSIS is designed to take care the work done in the back end. Storing the file name and others make sense but rest is really confusing for anyone who have to maintain or troubleshoot the package. I would say simple is better.
Post #1006955
Posted Tuesday, October 19, 2010 8:10 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 4:49 PM
Points: 389, Visits: 154
The assumption that files coming in are of fixed length is little hard to generalize.

In that case the Configuration table values are hard to determine.

Great work in getting it up and running
Post #1006987
Posted Tuesday, October 19, 2010 8:38 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 6:37 PM
Points: 33,189, Visits: 15,329
Martyn Hughes (10/19/2010)
I don't know why you'd want to go to such lengths to use SSIS, just use Pervasive (formerly Data Junction). It's a far superior way of getting data into SQL.


Not everyone can afford third party tools, or get the approval to buy them. Knowing how they could perform this in SSIS is a piece of knowledge that many can benefit from.

If there's a superior way to use Pervasive, perhaps you would want to mention specifically why rather than just add a snarky comment.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1007007
Posted Tuesday, October 19, 2010 8:54 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Today @ 1:13 AM
Points: 150, Visits: 159
Thanks and nice work Sarah! But can you update it with link to source code. I know all the SQL scripts are in the content, but we need SSIS files too. Thanks in advance!
Post #1007025
Posted Tuesday, October 19, 2010 9:11 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Monday, December 16, 2013 10:42 AM
Points: 96, Visits: 434
Nitya (10/19/2010)
The assumption that files coming in are of fixed length is little hard to generalize.

In that case the Configuration table values are hard to determine.

Great work in getting it up and running


It's not a generalization if your suppliers have given you a data dictionary. Many of our data suppliers do the same. The files they give us are always formatted with these fixed field lengths in mind, which we must then TRIM before using properly. The only difference in our packages is we handle erroneous row lengths in the package.

Very interesting way of importing flat files. We also build specific packages for each of our files coming in from different suppliers, and it's a real pain. SSIS can handle a lot of different scenarios, but IMO it's not a simple enough process, as you have mentioned.

Good article. ... Need to think about the pros and cons of adopting it here. Thanks for sharing!


-------------------------------------------------------------------------------------------------
My SQL Server Blog
Post #1007049
Posted Tuesday, October 19, 2010 9:56 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Friday, November 12, 2010 12:19 PM
Points: 5, Visits: 17
Steve, I've been a great fan of SSC for many years, I've used a number of redgate tools and Litespeed to compress some rather large DBs especially when using a SAN. I think Susan made a good contribution to the forum.

My comment is not meant to be 'snarky', I'm always troubled when I have to fight within an organization to get useful tools. Pervasive does cost several thousand but the amount of time saved using appropriate tools rather than paying FTEs to 'reinvent the wheel' is certainly a better use of company resources.

Pervasive has data connectors for just about anything, even really old 132 column report type stuff! (Only useful if you're dealing with old mainframe stuff)

I've used it to convert Progress to Oracle DW, Progress to SQL and vice-versa, Foxpro to SQL. On a smaller scale I used it to convert Quickbooks to SQL.

SSIS is certainly better than the old DTS but far behind 3rd party tools.
Post #1007088
Posted Tuesday, October 19, 2010 10:11 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Wednesday, June 25, 2014 11:35 AM
Points: 4, Visits: 88
I appreciated you article on SSIS. It is timeconsuming to use SSIS in a lot of situations like yours.

You might be able to eliminate SSIS completely. You can use xp_cmdshell to run operations like ftp directly on the operating system. You can also unzip. Just build the commands you want.

Use insert / exec to pull the directory contents into the stored procedure.

Use bulk insert to load data into a database table. The format file option is great for fixed length records and the fastest way I know to load data.

Post #1007105
« Prev Topic | Next Topic »

Add to briefcase 1234»»»

Permissions Expand / Collapse