0
1
im a newbie with sql-server 2005. i build some packages which import some flatfiles into tables, each file goes into his table. Now there is a change in the structure of one file.
Now i am too stupid to change this package which is stored on the server in msdb. Please be kind and explain the steps to get the package in visual studio for editing, thx.
Ice
Posted 2009-12-16T18:08:40.817
Reputation: 599
3
I'm assuming you're talking about an Integration Services package, as these are the only "packages" that get deployed to the MSDB database :)
To edit a package that's been deployed to MSDB, you'll need to connect to the Integration Services instance on the server, locate the package, and export it as a .dtsx package.
Then you should be able to open it in Visual Studio, edit it, and redeploy if necessary.
Jeremy Smyth
Posted 2009-12-16T18:08:40.817
Reputation: 354
0
By package, I assume you mean table or similar.
The easiest thing you can do for SQL 2005 is download SQL Management Studio Express for free and then login,and you can delete, modify or do anything with any databases currently loaded in your SQL instance.
William Hilsum
Posted 2009-12-16T18:08:40.817
Reputation: 111 572
Sorry, it's my fault; i mentioned no table. As i'm not so familiar with that ssis-thing... – Ice – 2009-12-16T20:14:03.650
sorry, my fault, I missed the term package! still, download Management Studio Express - as per your comment on Jeremy's answer, Management Studio Express is probably what you are looking for. – William Hilsum – 2009-12-16T20:36:26.023
Management Studio Express has no features that allow modification of SSIS packages. Sorry, your answer has no relevance to his problem :) – Jeremy Smyth – 2009-12-19T11:03:27.460
Sounds like the way i did it some months ago. i'm not familiar with that sql-2005 thing, but isn't it possible to manage them like sql-2000? At my point of view it's an overkill to do something like exporte as *.dtsx an reimport it - is that the truth? I'm very confused. – Ice – 2009-12-16T20:10:59.260
SQL 2000 used something called DTS (Data Transformation Services) to do what Integration Services does. Integration Services allows you to edit the source of the files (allowing e.g. source-code control), run the files directly without deploying, deploy to multiple servers, etc., all of which DTS made quite hard. The cost, of course, is that you have to use Visual Studio to edit the packages, where in SQL 2000 it was all done in Enterprise Manager :) – Jeremy Smyth – 2009-12-17T16:58:09.553
You are right, but me as a database passionate everything in the filesystem is evil... – Ice – 2009-12-17T22:40:36.523