• akin.akinwumi (6/15/2012)


    opc.three (6/15/2012)


    akin.akinwumi (6/15/2012)


    Copy your linked server query into an 'Execute SQL' task in SSIS. That way you get the best of both worlds!;-)

    In my opinion that is actually the worst of both worlds. You're bypassing the valuable functionality built into SSIS for data movement while still allowing SQL Server to SQL Server communication. Sorry, but it is hard to imagine a worse decision being made in this scenario :sick:

    We will have to agree to disagree on that point. In some scenarios based on how the database servers are set up; a linked query will produce better performance that SSIS data flow task! So if you still intend to use the performance gain of the linked query but still require that the data flow matched with your ssis package architecture? Well, SSIS provides the functionality to do that.

    Use a 'EXECUTE SQL' task. 😉

    All things being equal, even if you could not get an SSIS package to perform as well as a Linked Server setup (which I doubt) having SSIS push a process that does SQL Server to SQL Server communications in this manner is a ridiculous design pattern. Think about the debug scenarios and the environment maintenance required to support your proposed architecture. It is in the running for my last resort option.

    You're right about two things. 1. It depends, but only because that is almost always true. 2. I disagree with you.

    There are no special teachers of virtue, because virtue is taught by the whole community.
    --Plato