title: SSIS deployment best practices - package and other artifacts
body: <p>In my environment most SSIS packages are stand alone, and only the package it self needs to be deployed to production. </p>
  
  <p>However now we have a fairly complex set of packages that need their own tables to be created, and I'd like to be able to check permission at install time if possible. </p>
  
  <p>We have considered creating an MSI to do the production install using a step by step wizard. </p>
  
  <p>My question: is there a best practices for a SSIS deployment scenario such as this? Can we possibly hijack the deployment wizard SSIS generates by default to add our own steps? Is there any Microsoft documentation/guidance around this?</p>