October 1, 2008 at 11:08 am
I'm slowly learning how to use SSIS2005 and while I am enjoying learning what SSIS can do, I have to admit it's very frustrating trying to follow it all because there seems to be a lot that just doesn't make sense.
I have create an SSIS Package that works like I ant right now but will need some tweaking at a later time so it's not finished. I can execute the package from within the BI Dev Studio and get what I want from the package. I recently read a piece on the SQLSeverCentral website that showed how to execute the package from within SQL Server Management Studio. I decided to load the package via the Import Package feature so it could be run from within the same application (SSMS) that I spend most fo my day; it's just a convience thing.
Well now I need to make some change to the SSIS package and darned if I can figure out how I can edit the package that I imported into the MSDB foldre of packages which is visibile under the Stored Packages folder that you get in SSMS 2005 when connected to SSIS on an isntance of SQL Server 2005.
It looks like there is no way to do this, to change the original SSIS package. Is that a correct statement that once a package is imported it can't be edited? That you have to open and edit the orginal SSIS files, assuming you stioll have them, and then re-import the thing?
The whole thing is very confusing and any light that anyone could shed on this would be most appreciated.
Thanks
Kindest Regards,
Just say No to Facebook!October 1, 2008 at 11:36 am
I am not an expert on this, but from what I understand once you import the SSIS package into SQL server it is in a compiled form and the only way to make changes is to go to the original source code in SSIS. This is similar to the process that is required when working with other VS componenets such as c# as in you can not make changes to a compiled package only to the source.
October 1, 2008 at 12:27 pm
You can open and edit a package that is stored in msdb. After you've opened a solution in BIDS, right-click on SSIS Packages and select "Add Existing Package". In the window that opens, specify "SQL Server" as the location and the instance name as the server. Then click on the button for Package Path and select the package you want to work on.
When you're finished, save the package back to SQL Server.
Greg
October 2, 2008 at 6:05 am
You can also right-click on a package from within Management Studio and export it to the file system. SSIS packages never get "compiled". They are XML definitions, not compilable source code.
October 3, 2008 at 7:15 am
Like the others said, you can export it, but you really want to do is keep a copy in a development environment and always make your changes there, test, and once you are happy with the results, then push it to your server. It should also be in some kind of source control (SVN,VSS, TFS, IconForge, etc.) so you can version your packages and easily rollback if needed.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply