January 28, 2010 at 10:49 am
I will admit that I am very much a newbie with regards to SSIS but i am analytical and can generally follow something that has a logical structure but when it comes to SSI, forget-about-it. I'm hoping one of you SSIS gurus can educate me on this.
We have recently taken over a new server (actually more then a server but for this post lets isolate this to a single server) that is running SQL Server 2005 with SSIS packages on it and running. One of theSQL Jobs calls an SSIS package, a package that is stored in the SSIS store (excuse me if I'm using the wrong name/term here). What I mean by that is when I look at Package path specified in the 'GENERAL' tab within the individual STEP detail of this job I see the following where MYSQLSERVER is the name of thh SQL Server box:
MYSQLSERVER\DTS Packages\Copy Database Wizard Packages\CDW_MYSQLSERVER_MYSQLSERVER_0
Now I know that I can load SSMS 2005 and connect to the SSIS service on MYSQLSERVER and naviagte within it down to STORED PACKAGES
and then MSDB
and then MYSQLSERVER
and then DTS Packages
and then Copy Database Wizzard Packages
where there is a single diretcory labeled CDW_MYSQLSERVER_MYSQLSERVER_0
This path matches the path outlined in the SQL Job Step. What I can't do from here is find out exactly what this SSIS thing does. No where can I find anything that tells me the SSIS project or dtx file or anything that will tell me how in BI Dev Studio I can load this thing and see exactly what its doing.
What am I missing or doing wrong? How does one discover exactly what an SSIS package is doing that is setup in SQL Server when they do not know the source SSIS package files used to make that SSIS package?
Please tell me its really simple and that I'm just mising something simple because I really want to like SSIS but it's things like this that make it a very difficult thing to even like.
Thanks
Kindest Regards,
Just say No to Facebook!January 28, 2010 at 10:53 am
Have you looked at exporting the SSIS package to the file system? I haven't done this, as our SSIS packages are also stored in VSS and if we need to look at them, that is where we go.
January 28, 2010 at 11:08 am
I think Lynn is correct: export the package out into the file system and then open it in BIDS to see what the steps are doing ...
By the way, I was a bit disappointed to see no mention of string theory in the body of your message 🙂
The absence of evidence is not evidence of absence.
Martin Rees
You can lead a horse to water, but a pencil must be lead.
Stan Laurel
January 28, 2010 at 4:53 pm
Create a new Integration Services project in BIDS. Right-click on the SSIS Packages folder and Add Existing Package.
In the dialog box, select the correct package location, the server and select the package you want to work with. To publish the changes, you reverse the process by saving a copy of the package to the SSIS Package Store or SQL Server (or file system).
Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”
― Charles R. Swindoll
How to post questions to get better answers faster
Managing Transaction Logs
January 29, 2010 at 4:23 pm
Lynn Pettis (1/28/2010)
Have you looked at exporting the SSIS package to the file system? I haven't done this, as our SSIS packages are also stored in VSS and if we need to look at them, that is where we go.
I had not and thank you for pointing this out. I knew there had to be some way to do this. I guess just letting one diretly access and look at the package like one can do with T-SQL in a old fashioned SQL Job was asking for too much from SSIS when they put it together.
Thanks to the other replies to; all great suggestions.
Phil - Sorry about the lack of String Theory info but I figured problems/issues with SIS alone were enough of a headache without adding anything else complex to the mix 🙂
Kindest Regards,
Just say No to Facebook!Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply