Databases
StackOverflow2013
Postsdbo
POSSIS 2012 Project Deployment Model - Environment Inheritance
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POSSIS 2012 Project Deployment Model - Environment Inheritance
    primarykey
    data
    text
    <p>We have three environments - production, staging, and test. Each environment has multiple databases for our internal back office systems (ie, time collection, accounting, human resources, etc).</p> <p>For our employee benefits, we create file feeds that get shipped out to our benefit providers to handle enrollment/termination. Prior to SSIS 2012, we had a set of custom SSIS components that centralized configurations - so depending on where we deployed the package, it would automatically pick up the right connection strings.</p> <p>Now our old way worked, but it has its own difficulties (ie, new developers often forget to set up the package properly and spend time trying to figure it out), so we'd like to move forward with SSIS 2012 and the Project Deployment Model.</p> <p>I really like the concept of the Environment configurations, but simply creating 3 environments for prod/stage/test doesn't seem like a good idea. A lot of our packages have custom SFTP credentials, file paths to various areas on the network, etc - so those environments would grow very quickly with things that don't really matter to most of our packages. </p> <p>Is there a way to have one Environment configuration pull in data from another Environment configuration? Something like this would allow me to create a Production Environment config which has the common database servers, and then inherit that within a production config for one of our benefit file feed packages. The benefit file feed package prod config would have all of its other very specific variables. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. This table or related slice is empty.
    1. USMike Pugh
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POSSIS 2012 Project Deployment Model - Environment Inheritance
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POSSIS 2012 Project Deployment Model - Environment Inheritance
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI don't think you will be able to do what you want with the default options available in the SSIS Catalog. It is however quite easy to modify the SSISDB through T-SQL. But if you really want to go through the trouble of writing something custom depends on how many parameters you expect to use. I don't see any problems with creating just the 3 different environments.
      singulars
      1. POSSIS 2012 Project Deployment Model - Environment Inheritance
      1. USJodyT
    2. CO@JodyT - Well the goal was to not have 3 environment configs, each with well over 50 variables to handle the needs of all of our different packages. Our production environment has numerous systems in place to support our company, so we'd prefer to keep the SSIS Environment Configs focused. But it doesn't look like SSIS 2012 supports this very well. Not that big of a deal.
      singulars
      1. POSSIS 2012 Project Deployment Model - Environment Inheritance
      1. USMike Pugh
    3. COOnce you have more than a few vars in a package, handling them inside SQL can be a pain, so in that case one strategy I have used is to have one var pointing to a location like a config file or view that holds all the properties, which the ssis package reads in as part of its initialisation. Then in the different environments, you only have one parameter to manage (inside of SQL Server, anyway).
      singulars
      1. POSSIS 2012 Project Deployment Model - Environment Inheritance
      1. USmeataxe
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload