Post reply

Storing values of package variables in user table in any database

  • August 2, 2018 at 7:05 pm

    #355238

    Is it a good practice or not instead of using configs/xml/text/etc.  just
    create 1 table somewhere with columns like 
    VarName, VarValue, PackageName, VarScope, IsProduction, ... etc.
    and then retrieve them via a simple executeSQL task at the start of the package?

    I am not finding anything on the internet about such simple and straightforward way of saving runtime variables outside the package.

    If someone has an opinion on that please share.
    Thank you.

    Likes to play Chess

  • August 2, 2018 at 11:08 pm

    #2000114

    VoldemarG - Thursday, August 2, 2018 7:05 PM

    Is it a good practice or not instead of using configs/xml/text/etc.  just
    create 1 table somewhere with columns like 
    VarName, VarValue, PackageName, VarScope, IsProduction, ... etc.
    and then retrieve them via a simple executeSQL task at the start of the package?

    I am not finding anything on the internet about such simple and straightforward way of saving runtime variables outside the package.

    If someone has an opinion on that please share.
    Thank you.

    As always, it depends!
    😎

    Suggest you search for "SSIS configurations in a database", plenty of material out there. Further, SSIS has the option of storing configurations in the SSIS database.

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

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