Post reply

SSIS package version control

  • March 3, 2008 at 8:35 am

    #187268

    Is anyone using any sort of version control tools for SSIS packages? If so, what are you using and how has it worked out for you?

    Thanks,

    Tim

    Tim Mitchell
    TimMitchell.net | @tmitch.net | Tyleris.com
    ETL Best Practices

  • March 3, 2008 at 8:57 am

    #784479

    I am working with Team Foundation Server to do the version controling with SSIS which seems to be a great tool.

    It is intergrated with Visual Studio so that you have less troubules.




    My Blog: http://dineshasanka.spaces.live.com/

  • March 5, 2008 at 1:45 pm

    #785742

    I'm using Visual Source Safe. It's not bad if you can set up the project structure correctly; I'm still trying to find the optimal structure. Do you put all 'files' associated with a package in one project and shared into a separate one, or do you put each 'file' type into its own folder?

    Tim

  • March 6, 2008 at 9:38 am

    #786122

    We're using TortoiseSVN and it works like a charm. Searching for previous versions is great and the software is free.

    Matt H.

  • April 17, 2008 at 3:03 pm

    #804018

    Matt Horton (3/6/2008)

    We're using TortoiseSVN and it works like a charm. Searching for previous versions is great and the software is free.

    Matt H.

    How does it integration with integration services? no pun intended 😉

  • April 17, 2008 at 3:32 pm

    #804033

    It's basically file based, so you check in the solution that your working with and then commit changes to the dtsx files as they occur. It's worked well for us so far.

    Matt H.

  • April 17, 2008 at 3:37 pm

    #804039

    cool, thanks.

    it would be super-great if microsoft would add a "date modified" to their summary report in integration services proper, or a right-click to show information about a package, such as when it was loaded into integration services... but that's just me wishing.

  • May 1, 2008 at 12:46 pm

    #809774

    Is there a way to see when the SSIS package is modified? or any version history available from system table/view?

  • May 1, 2008 at 12:52 pm

    #809775

    You can search for previous versions through SVN, but SQL server doesn't store previous versions as far as I am aware.

  • May 1, 2008 at 1:14 pm

    #809790

    Thank you Matt.

    system table dbo.sysdtspackages90, Is createdate column for originally “created” date only? If any change/modify for SSIS package, does the column reflect the change respectively which means showing the modified date?

  • May 1, 2008 at 7:36 pm

    #809879

    Very cool table. One I didn't know about. In my testing tonight, it's the original create date of the package.

  • May 2, 2008 at 6:14 am

    #810017

    If this table had a "modifydate" column I would be a happy camper.

  • May 2, 2008 at 7:39 am

    #810070

    The createdate column in sysdtspackages90 is not automatically generated. It is a package property you have to set/update each time you make a change. The only property I believe that is auto-incremented is the verbuild property.

  • May 2, 2008 at 7:57 am

    #810086

    Thank you Gordon.

    So if verbuild = 0 means no change after SSIS pkg is deployed? If it was modified/re-deployed, the verbuild will become to 1?

    I have an urgent need to find out whether a SSIS pkg is changed or not.

  • May 2, 2008 at 8:23 am

    #810102

    Actually I believe anytime you perform a build/rebuild on the package, the verbuild number is incremented.

Viewing 15 posts - 1 through 15 (of 56 total)

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