Post reply

add pacakge

  • February 13, 2012 at 2:20 pm

    #268218

    Once a while, I need to make a small changes on an exiting package on the server.

    I usually open the .dtsx file, and edit and save it.

    It works fine. But since it is on the produciton server, there is no solution file there, but only .dtsx file.

    I cannot excute it unless I use sql agent job or dtsx execute tool.

    But I sometimes just create a temp project on the server, and then add the exisiting package to the server. This way I can edit it, but I can also execute it in the bids.

    My question is when I add existing pacakge, it seem it added to the project directory as a new file, so if I edit it, I didn't actually do it on the original file.

    How can I add the existing package without changing the original path of it?

    Thanks

  • February 13, 2012 at 2:35 pm

    #1446520

    Short of editing the project file itself I don't think you can.. However, when you are done editing just copy the file back to the original location..

    CEWII

  • February 13, 2012 at 2:40 pm

    #1446527

    Thanks, that makes sense, will do that way.

  • February 14, 2012 at 12:08 am

    #1446648

    sqlfriends (2/13/2012)

    Once a while, I need to make a small changes on an exiting package on the server.

    I usually open the .dtsx file, and edit and save it.

    It works fine. But since it is on the produciton server, there is no solution file there, but only .dtsx file.

    I cannot excute it unless I use sql agent job or dtsx execute tool.

    But I sometimes just create a temp project on the server, and then add the exisiting package to the server. This way I can edit it, but I can also execute it in the bids.

    My question is when I add existing pacakge, it seem it added to the project directory as a new file, so if I edit it, I didn't actually do it on the original file.

    How can I add the existing package without changing the original path of it?

    Thanks

    Change management wise, this is a nightmare.

    You shouldn't develop directly on a production server, but develop hotfixes on a seperate environment, test them there and then push them to production.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • February 14, 2012 at 8:12 am

    #1446860

    Koen,

    You certainly have a point, this is not good code control. And perhaps a way to negate the issue entirely. If he is always starting form the source controlled version then his path is always the same. check it out, modify, test, modify, test, modify, test, deploy.

    And as a side point, I never treat the code on the server as definitive, source control is to be defininitive. Basically I should be able to build the skeleten of the database or other items completely from source control..

    CEWII

Viewing 5 posts - 1 through 5 (of 5 total)

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