|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
ETL Tools for EDI to DB ImportHello,
We're trying to come up with a solution for loading large EDI (X12) batch files into a SQL Server 2005 system. We tried using Altova Mapforce which now has a code generation feature which can be compiled and run, but it does not seem to scale well for large data loads. Any one have any other suggestions for tools to help import large EDI X12 flat files with really complex data structures? Thanks, JGP SSIS
sql server integration services -- Show quotethanks, ------------------------------------ Jose de Jesus Jr. Mcp,Mcdba Data Architect Sykes Asia (Manila philippines) MCP #2324787 "Joseph George" wrote: > Hello, > > We're trying to come up with a solution for loading large EDI (X12) > batch files into a SQL Server 2005 system. > > We tried using Altova Mapforce which now has a code generation feature > which can be compiled and run, but it does not seem to scale well for > large data loads. > > Any one have any other suggestions for tools to help import large EDI > X12 flat files with really complex data structures? > > Thanks, > JGP > > Many, if not most of the major data integration vendors support EDI
metadata. Here's a list of some of them. www.abinitio.com www.ascential.com www.datamirror.com www.datawatch.com www.embarcadero.com www.informatica.com www.pervasive.com -- David Portas SQL Server MVP -- Thanks for the responses.
I'm kind of new to this EDI import thing. So pls forgive me if this question sounds basic.. Is it better to convert large EDI flat file to XML first and then load into relational database. Rather than loading directly into database. We will have to do data-cleansing & validation at some point as well. Thanks for any insights, JGP |
|||||||||||||||||||||||