January 24, 2017 at 10:04 am
Hello,
I have a job that that has steps that calls integration packages, that is not a scheduled or deployed.
I have tried to use VS15 as File, New. Project, select Integration Services Import Wizard, and when I nav to the dir when everything has generally been kept, (taking over from a consultant), there isn't a project folder of solution file that correlates to the job that is out there.
I need to copy it as I need to change the target to a different cube name.
I thought this was the best way to make a copy of the original and to mod the copy, but it seems to be untouchable, and I cant find his original work files.
It's as if he created this as New, right in the Jobs area in the SQL Server Agent??
Many thanks for help in understanding.
JPQ
January 24, 2017 at 1:10 pm
quinn.jay - Tuesday, January 24, 2017 10:04 AMHello,
I have a job that that has steps that calls integration packages, that is not a scheduled or deployed.
I have tried to use VS15 as File, New. Project, select Integration Services Import Wizard, and when I nav to the dir when everything has generally been kept, (taking over from a consultant), there isn't a project folder of solution file that correlates to the job that is out there.
I need to copy it as I need to change the target to a different cube name.
I thought this was the best way to make a copy of the original and to mod the copy, but it seems to be untouchable, and I cant find his original work files.
It's as if he created this as New, right in the Jobs area in the SQL Server Agent??
Many thanks for help in understanding.
JPQ
SQL Agent jobs and SSIS packages are separate things. The packages need to be created first, then deployed, and then the SQL Agent job is created to execute the deployed packages.
Bearing all of that in mind, would you clarify your question please?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
January 24, 2017 at 1:36 pm
What method of Deployment have they actually used (are they actually deployed)? you can run an SSIS package from several locations, the SSIS Catalog, SSIS Package store, or file system (this isn't really deployment). Which has been used?
If using a file system method, it's very likely that they haven't put the project files there, as there's no requirement.
Thom~
Excuse my typos and sometimes awful grammar. My fingers work faster than my brain does.
Larnu.uk
January 24, 2017 at 1:56 pm
Phil Parkin - Tuesday, January 24, 2017 1:10 PMquinn.jay - Tuesday, January 24, 2017 10:04 AMHello,
I have a job that that has steps that calls integration packages, that is not a scheduled or deployed.
I have tried to use VS15 as File, New. Project, select Integration Services Import Wizard, and when I nav to the dir when everything has generally been kept, (taking over from a consultant), there isn't a project folder of solution file that correlates to the job that is out there.
I need to copy it as I need to change the target to a different cube name.
I thought this was the best way to make a copy of the original and to mod the copy, but it seems to be untouchable, and I cant find his original work files.
It's as if he created this as New, right in the Jobs area in the SQL Server Agent??
Many thanks for help in understanding.
JPQSQL Agent jobs and SSIS packages are separate things. The packages need to be created first, then deployed, and then the SQL Agent job is created to execute the deployed packages.
Bearing all of that in mind, would you clarify your question please?
Yes, SQL Agent, has a job, that calls several packages, and I need to copy it to a solution file so I can redesign a package in it to change the target cube.
What I'm learning, is I can't copy out of the SQL Agent like I can an existing SSIS package with Wizard import. I'm also realizing that the packages in the SQL Agent Job, are calling existing packages used in another production job, so I would ultimately need to copy those packages.
So as this is winding up, being on one box for both Dev and Prod and now VC (I know, I know), and wanting to run a process that reloads all historical data once a year, but this time not do it straight against the production cube..., I'm going to have to Wizard/Import to a new solution the existing prod deployment, and delete out the unwanted packages, and leave the ones I need, and refashion it to look like the same components and processing logic as whats in the SQL Agent Job.
January 24, 2017 at 2:02 pm
Thom A - Tuesday, January 24, 2017 1:35 PMWhat method of Deployment have they actually used (are they actually deployed)? you can run an SSIS package from several locations, the SSIS Catalog, SSIS Package store, or file system (this isn't really deployment). Which has been used?If using a file system method, it's very likely that they haven't put the project files there, as there's no requirement.
It appears they dis a File New in SQL Agent and plugged in existing SSIS packages and they go to a specific Cube name. I just gave a details post a moment ago, and I explain more of what I've figured out. Ultimately I'm not going to get to make a Wizard/Import type copy to mod the SSIS Package within. More complex than that, but it's turning into a "it is what it is", as I've under covered a shortcut, and to get what I want is a project.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply