Home Forums Data Warehousing Integration Services Issues and performance of importing XML into SQL Server 2008 RE: Issues and performance of importing XML into SQL Server 2008

  • October 7, 2015 at 8:20 pm

    #1832198

    Sideout1972 (9/28/2015)

    XML structure that goes more than 2 levels deep performs horribly with SSIS during the development cycle. Drop-downs where you are picking a node could take minutes, and even hours to load if the XML has a complex structure.

    The only reasonable performance comes with using openrowset, XPATH, etc.

    Using SSIS best practices isn't always the best performing way of accomplishing a task.

    Amen to that. Same goes for XML in general, IMHO. Between the tag bloat and the other problems associated with it, it's just easier to go with a nice, properly normalized, properly delimited flat file.

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)