Answered SSIS Package Configuration

  • Monday, February 04, 2013 3:05 PM
     
     

    Hello,

    As per following article, "You cannot use the /Set or the /Connection option to override single values that are also set by a configuration". Can you elaborate on this with example?


    msdn.microsoft.com/en-us/library/ms141682.aspx

    My other question is if we want to schedule an SSIS package, can I schedule the package without running the BUILD command and preparing a DeploymentManifest. If not why?

    Thanks

All Replies

  • Monday, February 04, 2013 3:26 PM
    Moderator
     
     Proposed

    It is as simple as the config takes the precedence over the /Set or /Conn switches.

    You can, the DeploymentManifest is needed only once when you deploy a new package or an update. Build is basically emitting the new package file.


    Arthur My Blog

  • Tuesday, February 05, 2013 3:16 AM
     
     

    Agree with ArthurZ.

    By the way, you can also get SSIS packages deployed via SSMS by navigating to the folder on the SSIS Instance, right clicking and selecting Import Package. Simply browse to the file system folder where the package is held.

    I have also used T-SQL commands to SELECT a package out of one MDSB and insert it into another. (Shshshshs. Don't tell my boss, he didn't know! I wasn't supposed to have access to deploy packages in Production, and could not connect to SSIS Instance due to firewall issues. BUT, I did have full access to the MSDB databases in both TEST and PROD environements, and a linked server between the two. Knowing the MSDB table structure holding SSIS packages and folders, I was able to insert an SSIS package, essentially a binary file, from one server's MSDB database to another's)


    Todd C - MSCTS SQL Server 2005, MCITP BI Dev 2008 Please mark posts as answered where appropriate.

  • Tuesday, February 05, 2013 8:15 AM
     
     
     But what does single values that are also set by a configuration mean. Whats single values in configuration?
  • Tuesday, February 05, 2013 1:04 PM
     
     Answered

    Have you experimented with SSIS Configurations of ANY type? (XML File, SQL Table, Parent Package, etc?) You can set a value, that is a property setting or variabel value or connection string or any other single point in your package by storing that value (and the path to it inside your package) OUTSIDE the package. Then, when the package runs, it go and gets that value, sets it accordingly, and runs the package. It's the difference between Design-time values and Run-time values.

    Here's the great thing, the 'path' to that externally saved value is relative to where the package is being run from. So if it is a local SQL table, when you move the package to another server, that server can have a copy of that table, but store different values (new Run-Time values).


    Todd C - MSCTS SQL Server 2005, MCITP BI Dev 2008 Please mark posts as answered where appropriate.