Modify and saving SSIS package

  • Hi,

    I changed one of the ssis package by opening it from file location and saved it by just clicking save button in visual studio and then importing it in ingration services by overwriting.

    Is that good enough or do I need debug it before I can use the modified package?

    THanks.

  • sql_novice_2007 (7/6/2011)


    I changed one of the ssis package by opening it from file location and saved it by just clicking save button in visual studio and then importing it in ingration services by overwriting.

    Is that good enough or do I need debug it before I can use the modified package?

    That depends upon how confident you are in your changes? 🙂

    Are you using source control? Do you need to check changes into your repository?

    How are you trying to run the modified SSIS package (DTSEXEC, SQL agent job, ...)?

    Is the package being maintained by SQL Server or by the file system?

    Rob

    P.S. Your question might be better placed in the SSIS forum under Data Warehousing

  • The only thing to be aware of is that SSIS wipes any sensitive information (i.e. passwords for connections) when you open the package if you don't decrypt it correctly.

    Since the package file is xml you can change whatever you like: so long as the xml is valid you can run it (no debugging necessary). Unless you've introduced any other errors 😉

  • sql_novice_2007 (7/6/2011)


    I changed one of the ssis package by opening it from file location and saved it by just clicking save button in visual studio and then importing it in ingration services by overwriting.

    Is that good enough or do I need debug it before I can use the modified package?

    You're asking the wrong people. Speak to your boss if he's willing to be woken up at 3 AM because you deployed an untested package. You'll also need to speak with them about if they use source control.

    This is about your environment, honestly, since I'm not the one being woken up at 3 in the morning for your lack of debugging and version control. If you're that confident... Go for it! :w00t:


    - Craig Farrell

    Never stop learning, even if it hurts. Ego bruises are practically mandatory as you learn unless you've never risked enough to make a mistake.

    For better assistance in answering your questions[/url] | Forum Netiquette
    For index/tuning help, follow these directions.[/url] |Tally Tables[/url]

    Twitter: @AnyWayDBA

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

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