August 12, 2011 at 4:32 pm
We have an DTS with a number of versions. After making changes, I saved the package and it is the latest version. When I Right click the package and choose Execute Package, it seems to be running the older version i.e., the one before making the changes.
Is there any setting that I should modify to run the latest version of the DTS. Because, previously, there was no need to manually select the version and run the dts.
August 12, 2011 at 5:14 pm
When manually running, this seems to be the norm.
When run from a job, it will run the latest version.
If you know for certain that you no longer need the prior versions, you may want to remove them from msdb. I would consider dumping them in source control first.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
August 12, 2011 at 8:11 pm
Hi Jason,
When I right click the package and give execute package, we would not be getting the versions. it starts executing. I was under the impression, that in such cases, the recent version would run.
As for the cleaning up older versions, we have kept it as a last option, if nothing else works.
August 12, 2011 at 9:50 pm
The following post may be of help to you.
http://www.sqlservercentral.com/Forums/Topic864318-148-1.aspx#bm864417
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 12, 2011 at 10:12 pm
Hi,
thanks for pointing to the post. I have the exact situation given in that post (copied below):
Question #2:
One of my packages calls a child package. But I keep getting an error saying that the parent package is expecting a child package with a specific GUID. I can't remember the exact error, but somewhere along the lines of "The package with ID.VersionID {A234-5435435-345345-fe4} expected does not exist.". In other words, it looks like the parent remembers the GUID of the child package and expects it to be there every time. [/size]As given in that post, I browsed the chose the correct child package. The thing is when that particular parent pkg version is run, it runs fine. But when we just execute the package, it fails with the same error as mentioned above.
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply