• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 340
  • Last Modified:

Different SQL Server Job Problem

I had another problem with another Job. I had to update the SSIS package in order to FTP data from different Vendor. And tested the package. It works fine and the data was processed and saved as it should. After that I saved the Package and add updated the Job by re-saving the package data. But it seems to me that the Job somehow still is hooked up to old package.
I have SQL 2008 R2, SSMS 2005 and SSIS Packages are created in MS Visual Studio 2005. Any suggestions?
0
Burzhuin
Asked:
Burzhuin
  • 7
  • 4
  • 3
  • +1
2 Solutions
 
Ryan McCauleyData and Analytics ManagerCommented:
Are you saying that you replaced the existing package and left the SQL job untouched, or that you deployed the new package to your server and updated the sql job to point to the new package? In either case, the sql agent shouldn't have a problem picking up the new copy of the package - are you sure your job is directed to use the correct one?
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
can you try exporting the package to the server ?
0
 
BurzhuinAuthor Commented:
Yes, I am sure of that. In order to make sure I saved the Package under different name, but in the same Custom folder. And I updated the Job to point to the correct package.
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
BurzhuinAuthor Commented:
By exporting your mean Save Copy of the Package As...?
0
 
Ryan McCauleyData and Analytics ManagerCommented:
I'm not sure how it could be running the old package if you'd saved the package using a new name, and then updated the job to use the new package. Are you sure you're edited the right job?

I don't mean to sound dismissive, but I haven't heard of any other cases where the SQL Agent continued to run an old version of a job after the admin updated the job step, and that seems to be what you're describing here.
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
use import export wizard from ssis, import from your flat file and export to the destination server
0
 
BurzhuinAuthor Commented:
I ran the Job after saving new Package and the Job update. That when I noticed that the Job does not work. It did not FTP the file but created empty one. That can happen only if old package was still running. The new package I tested and it works all way through. But somehow it does not call by the Job.
0
 
BurzhuinAuthor Commented:
@aneeshattingal: I am using SQL Server Business Intelligence Development Studion 2005. I never used import export Wizard. Actually I never even see one except when you created a new package. I would appreciate instructions here to go and what to click. Thank you.
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
My bad, import export wizard wont work ;
0
 
BurzhuinAuthor Commented:
I created new Test Job and used the same Package but IT STILL DOES NOT WORK. Is there any way to check the time stamp of saved package? Because it seems to me that when I Saved  Copy of Package As... it dis not overwrite the old one. But I saved it under different name. My brain is boiling already.
0
 
Eugene ZCommented:
where did you store your SSIS pack ? on what server?

check by using SSMS ->connect-> integration services-> your server --search your SSIS
if you are bot sure if it is old or new - rename ssis pack and upload the new one


from sql agent job -- select step properties -ssis- select pack..
if you run as dtexec with ssis in file system stored .. make sure it is the right pack nad use UNC path..

BTR: what error did you get?  again make sure to use UNC path (often in dev  local drive instead of UNC used and server does not know \does not see it ..
0
 
BurzhuinAuthor Commented:
I have the only SQL Server so my SSIS pack is stored locally. I followed  your advice but when I was prompted to connect to my SQL Server connection failed: "Connect to SSIS Service on machine DATASQL failed: The specified service does not exist as an installed service." I think it is because I have SQL Server 2008 R2 and SSMS 2005.
0
 
Eugene ZCommented:
ok
try SSMS 2008 2

or check fom sql agent job for ssis (it is not clear is it in MSDB on on your drive as  fiel)

see the example:
Scheduling SSIS Packages with SQL Server Agent
http://decipherinfosys.wordpress.com/2008/09/17/scheduling-ssis-packages-with-sql-server-agent/
\
see Scheduling the SSIS Package as a Job
0
 
Eugene ZCommented:
"Connect to SSIS Service on machine DATASQL failed: The specified service does not exist as an installed service":

means you do not have SSIS installed on DATASQL (check DATASQL ssis server  - it should be there if installed - or not when not installed - also it can be down)
0
 
BurzhuinAuthor Commented:
I checked and SSIS is actually installed on DATASQL server. The service is up and running.
0
 
Eugene ZCommented:
it is good

what about sqlagent access or using ssms 2008 r2 ?
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 7
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now