Post reply

Moving SSIS from sql Server 2005 to sql server 2012 - Receiveing errors.

  • July 18, 2014 at 2:11 pm

    #288042

    Hello,

    We are upgrading from SQL Server 2005 to SQL Server 2012, and I have several SSIS packages that were deleveloped in visual studio 2005, and run as SQL Server jobs. The SSIS packages that I am having trouble with are importing flat files into sql.

    In testing our SSIS packages from my PC through visual studio 2005, loading the files into tables into the new SQL Server 2012, I have no problems, I just change the paths that need to be changed run the packaged, and the files load just fine.

    When I add the SSIS Packages to a job on SQL Server 2012, I get a number of errors, mostly truncation errors. The only way I can seem to fix this is to ignore the truncation failure on the colums in the flat file import.

    The files we are importing have a header and footer that do not have the same number of columns or the same type of data that the rest of the file has. I can also fix the error by removing the footer record.

    I was wonder if there is a way to fix this with removing the footer or ignoring trucation error.

    Thanks,

    Sam

  • July 18, 2014 at 2:27 pm

    #1730766

    currently how are you handling the footer records in 2005? Isn't the same logic working for 2012?

  • July 18, 2014 at 4:07 pm

    #1730790

    I didn't change anything except for the connection to the new server with SQL 2012.

    Right now in my dataflow I have a flat file source, then I remove the header and footer with a conditional split, and that always worked before, but when I run the SSIS with SQL 2012 the package seems to fail on the flat file source before it gets to the conditional split.

    Thanks,

    Sam

  • July 18, 2014 at 4:30 pm

    #1730793

    I believe 2012 improved row sampling for determining if a file was going to fail metadata, but I'm not positive on that.

    Is this a CSV? If so, does your footer have commas? Can you have the CSV definition modified to allow both the standard data and the footer information in those columns fit?

    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]
    Twitter: @AnyWayDBA

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply