Post reply

Put logic inside Execute SQL Task or call sproc?

  • September 21, 2010 at 1:29 am

    #1224586

    I prefer SP's over Exec SQL Task most of the times. And if its a looping work, SP's are aways better. And we (nearly always) make a deployment plans right? So forgetting is not an excuse (just stick to the plan 😉 ). Somebody save da-zero by telling his 'god' to allow him to do what he wants 😛

    _____________________________________________________________

    [font="Tahoma"]'Some people still are alive simply because it is illegal to shoot them... o_O 😎 '[/font]

  • September 21, 2010 at 4:42 am

    #1224666

    theSuda (9/21/2010)

    Somebody save da-zero by telling his 'god' to allow him to do what he wants 😛

    These days we just call them "bosses". 🙂

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • September 22, 2010 at 7:45 am

    #1225589

    Another plus in the SP column is that if you have reusable sql in the Exec SQL task that is used in multiple packages (assuming no common child package is being called containing the sql task), you have to edit each individual package ... opening, editing, saving, re-deploying, etc.

    If each package calls the SP, then you just need to adjust the SP, and you're done.

  • September 22, 2010 at 8:20 am

    #1225625

    Thanks, guys. SPs appears to be the resounding favorite.

    ---------------------------
    |Ted Pin >>

Viewing 4 posts - 16 through 18 (of 18 total)

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