Post reply

which approach is better in terms of performance?

  • June 21, 2011 at 5:04 pm

    #242928

    Hi All,

    I am plannging to implement an sssis package for migration of data within a database.

    Approach 1:

    4 execute sql tasks will run parallel. All the four tasks will use one connection manager.

    Connection manager details: server A, Database A

    Approach 2:

    4 execute sql tasks will run parallel. All the four tasks will use four different connection managers.

    Note: but all the connections will point and connect to the same database.

    Connection manager details all four connection managers: server A, Database A

    My question is here: Whether any performance difference between these two differences?.

    Which approach is better.

  • June 21, 2011 at 5:49 pm

    #1342187

    Single Connection manager for ease of use, don't turn on the RetainSameConnection property (ie: Leave it False) and they'll each open an independent SPID.

    This is your best method unless you need transactionality.

    - 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

  • June 22, 2011 at 9:26 am

    #1342493

    I believe approach 1 is the best answer and I don't think there will be any performance hits. It will still open 4 connections anyway.

    CEWII

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

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