Coordinating SSIS Packages Across Dev, Test, Prod Servers

  • I have started a new engagement where there are SSIS packages across three different servers: DevServer, TestServer, and ProdServer. I need to find out if the SSIS packages in Prod are the same version as in Test and Dev and so on. Currently, I am running a query across each server to get the PackageName, verbuild, and createdate from msdb. Is there a way to do this dynamically, so we will be able to automate the coordination? We have several Dev, Test, and Prod servers I'm going to have to maintain.

  • No source control? At this point I would simply say that evrything in Prod is correct and the most recent (that is what you are using so it must have been developed and tested in QA). That would be my starting point. I would get all reverse engineered back into BIDS and saved in some sort of source control program.

  • gary.mazzone (10/17/2011)


    No source control? At this point I would simply say that evrything in Prod is correct and the most recent (that is what you are using so it must have been developed and tested in QA). That would be my starting point. I would get all reverse engineered back into BIDS and saved in some sort of source control program.

    +1 to this.

    If you really need to look at it through the query I'd look into doing something with PowerShell to query across environments.

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

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