Answer by WilliamD
SSIS is the way to go IMO. Here at work we have some sort of dynamic SSIS implementation, where the control data is stored in sql server, allowing new file formats to be easily added without having to...
View ArticleAnswer by Pavel Pawlowski
If you know, that the source file format may change in the future, but the destination tables will remain the same, I go by SSIS, because in that case, when source file changes, you only update the...
View ArticleAnswer by Grant Fritchey
Deep down I know the answer is SSIS... If it's likely to change, you probably should take that into acount and write the import process in a language that can deal with it appropriately. I'd use...
View ArticleAnswer by TimothyAWiseman
I'm going to join with everyone else and say that if the file format is any one of the standard types (CSV, TSV, fixed width) that SSIS is the way to go. And this remains true even if you think the...
View Article
