March 13, 2013 at 8:32 am
Jeff,
Yes the connection is named the same(Configuration filter is reused in each package) across all the packages.
I find the error when I click on Edit package configuration.
March 13, 2013 at 10:49 am
Below is the error message I am getting when I try to set up table valued package configuration.I am referring the same configuration filter across all the packages.Since the SOURCE_DB and Destination_DB connection are not in package level I am not able to create the package configuration. This error message is shown after enabling th epackage config and when clicking on 'EDIT' .
TITLE: Microsoft Visual Studio
------------------------------
Some configurations from table "[dbo].[SSIS_Configurations_New]" with configuration name "Master" could not be loaded due to the following reasons:
\Project.Connections[Source_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[InitialCatalog]'.
\Project.Connections[Source_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[ConnectionString]'.
\Project.Connections[Destination_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[InitialCatalog]'.
\Project.Connections[Destination_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[ConnectionString]'.
------------------------------
BUTTONS:
OK
------------------------------
March 13, 2013 at 10:49 am
Below is the error message I am getting when I try to set up table valued package configuration.I am referring the same configuration filter across all the packages.Since the SOURCE_DB and Destination_DB connection are not in package level I am not able to create the package configuration. This error message is shown after enabling th epackage config and when clicking on 'EDIT' .
TITLE: Microsoft Visual Studio
------------------------------
Some configurations from table "[dbo].[SSIS_Configurations_New]" with configuration name "Master" could not be loaded due to the following reasons:
\Project.Connections[Source_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[InitialCatalog]'.
\Project.Connections[Source_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Source_DB].Properties[ConnectionString]'.
\Project.Connections[Destination_DB].Properties[InitialCatalog]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[InitialCatalog]'.
\Project.Connections[Destination_DB].Properties[ConnectionString]: The configuration refers to an object that does not exist in the package. Package path of the object: '\Project.Connections[Destination_DB].Properties[ConnectionString]'.
------------------------------
BUTTONS:
OK
------------------------------
March 13, 2013 at 11:16 pm
This is because you're trying to configure things that don't exist in the package. If you're sharing one configuration file (or configuration table) between packages, the packages need to have the same structure, at least to the extent that the paths to all the items being configured are the same.
John
March 15, 2013 at 1:16 am
If the job is run by SQL agent. Restart SQL agent. The altered env var will then get picked up.
March 15, 2013 at 2:39 am
Drndrb (3/15/2013)
If the job is run by SQL agent. Restart SQL agent. The altered env var will then get picked up.
No need. He's using a SQL table package configuration, not an environment variable.
John
March 15, 2013 at 12:58 pm
Ok Got it.Thanks.
March 18, 2013 at 3:24 pm
Hi,
Today I am facing problem when invoking multiple packages from a master package.
Here is the scenario.
Master Package has the below tasks conigured.
- For Each loop container (To loop through a folder for executing all the packages available in that folder)
-Execute Package Task (All the packages are placed in the file system)
Child Package :1
-consist of 3 Execute SQL task (Which is just a insert statement) -This package runs successfully.
Child Package:2
-consist of 2 Execute SQL task (Which is just a insert statement)
First SQL task runs good.
Second SQL task has syntax problem.
I have configured Checkpoint in all these Child packages.In my case -Child PAckage:1 runs successfully.But Child Package :2 fails at the second Execute SQL task.So my checkpoint works good when i do the needed modification.
But the issue is My For EachLoop container executes Child PAckage:1(Which should not happen) and then the Second Execute SQL Task (Which failed in first run).Because of the checkpoint file SSIS is not running the first Execute SQL task in the Chuld Package:2.
Please suggest how to keep track of failed package alone and to restart from that point.
Thanks
Nisha.V
March 18, 2013 at 5:00 pm
Can you not identify whether the rows previously inserted already exist and then do nothing if they do or insert them if they do not. That way you can just restart the packages and not have to worry about restarting from a certain point or inserting duplicate rows.
Check out: http://msdn.microsoft.com/en-us/library/ms140226.aspx
read the section 'Defining Restart Points'
you will see a comment regarding foreach loops
March 18, 2013 at 5:15 pm
Yes I can do that.But my concern is I am using "For Each loop" task for executing several child packages (Which makes million of rows to be loaded into the destination table). If I make the check condition (if the row exist or not) for every single package,it would be time consuming and the package may run for indefinite amount of time.So if there is any other way where I can call all the child packages from a master package and also if I could execute the package from the point of failure then that will solve my need.??
Thanks for your reply.
March 18, 2013 at 5:20 pm
One more question:
if a package runs successfully i want to move that package from that path automatically or it may be renamed.By doing this i believe this would eliminate the issue which i reported earlier.Because my master package will execute all the packages in the mentioned path and those packages which start with "T."
Is there a way that i can do it.
March 19, 2013 at 2:32 am
Do you have a definitive number of packages. If not, then execute each one in series connecting each one via an Success constraint. If one fails it should fail the parent package and the checkpoint will record the last point of execution.
Possibly, a foreachloop is not what you should be using.
March 19, 2013 at 10:50 am
i have around 140 packages 🙁
Viewing 14 posts - 31 through 43 (of 43 total)
You must be logged in to reply to this topic. Login to reply