Hi,
I'm currently organizing/deploying my SSIS projects as:
Integration Services Catalogs
SSISDB
Folder name matching the Project name
Projects
Project name
Packages
Package name.dtsx
Environments
Development
Production
Using this structure, I have to create an environment for each folder.
We only have a small number of servers and databases. It occurred to me that I could create an "uber" environment, with all the server and database names, regardless of whether a particular project uses that server and/or database.
The structure could look something like:
Integration Services Catalogs
SSISDB
CompanyName Projects (eg. Acme Projects) or just CompanyName (eg. Acme)
Projects
ProjectA
ProjectB
ProjectC
ProjectX
Environments
Development
Production
I would then only have to create the environments once. And, if the environment did ever change, I only have to modify it in one spot, and the change propagates to all the projects.
Your thoughts?
Yes, that's the way to go.
Though having Development and Production on the same server makes me shudder.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
October 15, 2019 at 3:09 am
I did think of one other approach:
Integration Services Catalogs
SSISDB
#Environments (just so this would sort as the top folder)
Projects
Don't put any projects here
Environments (Global environments that could apply to any/most projects)
Development
Production
Folder name (may or may not match the Project name)
Projects
Project name
Packages
Package name.dtsx
Project name
Packages
Package name.dtsx
Project name
Packages
Package name.dtsx
Environments
Don't put any environments here unless specific to this project/folder
Folder name #2
Projects
Project name
Packages
Package name.dtsx
Etc.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply